cortex_disable_responder · Cortex MCP: Risk & Policy

WHAT IT DOES

What cortex_disable_responder does on Cortex

AI agents use cortex_disable_responder to create or update resources in Cortex — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cortex environment.

WHY IT NEEDS A POLICY

Why cortex_disable_responder needs a policy

This tool modifies the state of a responder (removes/disables it) which is a reversible configuration change. It does not delete data irreversibly, execute arbitrary code, or cause financial impact. While it affects security infrastructure, the action can be undone by re-enabling the responder.

From the tool's definition Tool description states 'Disable (remove) an enabled responder from the current organization' - indicates modification of responder configuration state within an organization.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cortex_disable_responder Rate-limited

cortex_disable_responder stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cortex_disable_responder": {
      "limits": [
        {
          "counter": "cortex_disable_responder_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Cortex, so you can run agents against it safely.

FAQ

Questions about cortex_disable_responder

What does the cortex_disable_responder tool do? +

Disable (remove) an enabled responder from the current organization. It is categorised as a Write tool in the Cortex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cortex_disable_responder? +

Register the Cortex MCP server in PolicyLayer and add a rule for cortex_disable_responder: 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 Cortex. Nothing to install.

What risk level is cortex_disable_responder? +

cortex_disable_responder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cortex_disable_responder? +

Yes. Add a rate_limit block to the cortex_disable_responder 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.

How do I block cortex_disable_responder completely? +

Set action: deny in the PolicyLayer policy for cortex_disable_responder. 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.

What MCP server provides cortex_disable_responder? +

cortex_disable_responder is provided by the Cortex MCP server (solomonneas/cortex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.