Auto-detect and fix broken files, failed tests, and other issues. Returns list of healed items.
AI agents invoke cortex_auto_heal to trigger actions in Cortex MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs automated remediation by detecting and fixing files and running/fixing tests. It executes repair logic whose effects depend on the current state of the codebase. Since it modifies files (Write) and triggers external operations like test execution (Execute), and the scope of changes is broad and hard to predict, Execute is the most accurate category.
From the tool's definition 'Auto-detect and fix broken files, failed tests, and other issues' — actively modifies files and runs tests to remediate issues
Attacks that exploit this kind of access
Auto-detect and fix broken files, failed tests, and other issues. Returns list of healed items. It is categorised as a Execute tool in the Cortex MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_auto_heal: 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 MCP. Nothing to install.
cortex_auto_heal is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cortex_auto_heal 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_auto_heal. 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_auto_heal is provided by the Cortex MCP server (neuralnexustech/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 →