cortex_update_test · Cortex MCP: Risk & Policy

WHAT IT DOES

What cortex_update_test does on Cortex MCP

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

WHY IT NEEDS A POLICY

Why cortex_update_test needs a policy

This tool creates or modifies test records (marking them pass/fail), which is a reversible write operation. It does not execute code, delete data, or move money. Severity is medium because modifying test results could mislead development decisions or mask actual code quality issues if misused by an agent, but the blast radius is limited to test metadata rather than production systems.

From the tool's definition Tool name 'cortex_update_test' with description 'Pass or fail a test' modifies stored test state/results. The verb 'update' and the action of changing test status indicates data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cortex_update_test Rate-limited

cortex_update_test 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_update_test": {
      "limits": [
        {
          "counter": "cortex_update_test_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 MCP, so you can run agents against it safely.

FAQ

Questions about cortex_update_test

What does the cortex_update_test tool do? +

Pass or fail a test. It is categorised as a Write tool in the Cortex MCP 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_update_test? +

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

What risk level is cortex_update_test? +

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

Can I rate-limit cortex_update_test? +

Yes. Add a rate_limit block to the cortex_update_test 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_update_test completely? +

Set action: deny in the PolicyLayer policy for cortex_update_test. 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_update_test? +

cortex_update_test 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.