cortex_run_analyzer_file · Cortex MCP: Risk & Policy

WHAT IT DOES

What cortex_run_analyzer_file does on Cortex

AI agents invoke cortex_run_analyzer_file to trigger actions in Cortex. 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.

WHY IT NEEDS A POLICY

Why cortex_run_analyzer_file needs a policy

This tool executes an analysis operation on provided file input. While it doesn't directly delete data or move money, it triggers an external analyzer—a third-party security tool—with side effects that depend on the file and analyzer chosen. An attacker could submit malicious files to trigger unintended analyses, potentially causing system load, false security alerts, or information disclosure.

From the tool's definition Tool submits a file to an analyzer for analysis, triggering external analysis operations whose effects depend on the analyzer type and file content submitted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cortex_run_analyzer_file Rate-limited

cortex_run_analyzer_file stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_run_analyzer_file": {
      "limits": [
        {
          "counter": "cortex_run_analyzer_file_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_run_analyzer_file

What does the cortex_run_analyzer_file tool do? +

Submit a file to a specific analyzer for analysis. Provide a file path or base64-encoded content. It is categorised as a Execute tool in the Cortex MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cortex_run_analyzer_file? +

Register the Cortex MCP server in PolicyLayer and add a rule for cortex_run_analyzer_file: 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_run_analyzer_file? +

cortex_run_analyzer_file is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cortex_run_analyzer_file? +

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

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

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