# MCP connector controls and shared responsibility

You decide who can use the MCP connector, through the **TechWolf Agent** role, and TechWolf can switch it off for your whole organisation at once. TechWolf secures the connector and your TechWolf data, your AI tool's vendor secures the model and the conversation, and your organisation decides who connects, and with which AI tool.

## Admin controls

| Lever | Who uses it | Effect |
| --- | --- | --- |
| **TechWolf Agent** role | Your Console admins | Grants or removes a person's access. Removal stops their next call. |
| Data roles | Your Console admins | Limit which rows a person sees, as in the Console. |
| Organisation switch | TechWolf, at your request | Switches the connector on or off for your whole organisation, at once. |
| Connector settings in your AI tool | Your AI tool's admins | Decide who may add the connector, and which other connectors sit beside it. |

Every tool is available to anyone with the role, so tools cannot be switched off one by one. The data categories decide which tools return data for that person.

## Rate limits

| Tool | Per organisation | Per person |
| --- | --- | --- |
| Market search | 100 calls a minute | 20 calls a minute |
| Export queries | 60 calls a minute | 30 calls a minute |
| Every other tool | 20 calls running at the same time | No separate limit |

When the market search or export limit is reached, the connector tells the AI tool when to try again. Above the limit on the other tools, the call fails and the AI tool can try again. A market search returns at most 100 postings.

## Shared responsibility

| Area | TechWolf | Your AI tool's vendor | Your organisation |
| --- | --- | --- | --- |
| Identity and MFA | Requires sign-in through your identity provider; sets token lifetimes | Not involved | Runs the identity provider, MFA and leaver process |
| Who may use it | Checks the role and data access on every call | Not involved | Grants the **TechWolf Agent** role and data roles |
| Your TechWolf data | Hosting, encryption, tenant isolation, call records | Not involved | Decides what data is loaded into TechWolf |
| Questions, chat history and answers | Never receives them | Stores and processes them under your agreement | Sets retention, memory and training options in the AI tool |
| Model behaviour and prompt injection | Read-only tools that cannot send data out | Model safeguards | Decides which other connectors sit beside TechWolf |
| Switching off | Organisation switch | Connector settings | Removes the role; disables the connector in the AI tool |

## Your checklist

- Decide who gets the **TechWolf Agent** role, and review it regularly.
- Require MFA at your identity provider.
- In each AI tool's admin settings, decide who may add connectors and which connectors are allowed.
- Set your AI tool's retention, memory and training options to match your policy. The AI tool processes the TechWolf data it reads under those settings.
- Where your AI tool offers it, decide whether people approve each tool call.
- Tell people to approve a connection only when they started it themselves.

## Related pages

- [MCP connector security](/agent-integrations/mcp-connector/security)
- [MCP connector sign-in and access control](/agent-integrations/mcp-connector/security/sign-in-and-access-control)