Disable (remove) an enabled analyzer from the current organization. DESTRUCTIVE: requires confirm=true.
AI agents call cortex_disable_analyzer to permanently remove resources in Cortex — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly removes an enabled analyzer from the organization, which is a destructive action. Disabling/removing an analyzer could halt ongoing security analysis capabilities and cannot be trivially undone without re-enabling the analyzer. The server itself labels this as DESTRUCTIVE and requires explicit confirmation, indicating high impact and irreversibility in operational context.
From the tool's definition 'Disable (remove) an enabled analyzer from the current organization. DESTRUCTIVE: requires confirm=true.'
Attacks that exploit this kind of access
Disable (remove) an enabled analyzer from the current organization. DESTRUCTIVE: requires confirm=true. It is categorised as a Destructive tool in the Cortex MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_disable_analyzer: 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.
cortex_disable_analyzer is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cortex_disable_analyzer 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 cortex_disable_analyzer. 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.
cortex_disable_analyzer 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →