Hide a connector's tools from the active tool list for the current user. Use when the user says they don't use a service or wants to pause a connector, such as 'disable Shopify' or 'hide TikTok'. The connector remains configured and can be restored with enable_connector. Disabled connectors still...
Part of the CorpusIQ server.
Free to start. No card required.
AI agents use disable_connector to create or modify resources in CorpusIQ. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call disable_connector repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach CorpusIQ.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"disable_connector": {
"limits": [
{
"counter": "disable_connector_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full CorpusIQ policy for all 60 tools.
These attack patterns abuse exactly the kind of access disable_connector gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Hide a connector's tools from the active tool list for the current user. Use when the user says they don't use a service or wants to pause a connector, such as 'disable Shopify' or 'hide TikTok'. The connector remains configured and can be restored with enable_connector. Disabled connectors still appear in get_connector_status marked Paused.. It is categorised as a Write tool in the CorpusIQ MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CorpusIQ MCP server in PolicyLayer and add a rule for disable_connector: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches CorpusIQ. Nothing to install.
disable_connector is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disable_connector rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for disable_connector. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
disable_connector is provided by the CorpusIQ MCP server (https://mcp2.corpusiq.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 60 CorpusIQ tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.