cortex_run_analyzer_by_name · Cortex MCP: Risk & Policy

WHAT IT DOES

What cortex_run_analyzer_by_name does on Cortex

AI agents invoke cortex_run_analyzer_by_name 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_by_name needs a policy

This tool executes code/operations (an analyzer) in response to user input. While the analyzer itself may be a pre-defined security tool, the execution of arbitrary analyzers on user-supplied observables constitutes an Execute-category action.

From the tool's definition The tool 'run_analyzer_by_name' executes an analyzer against observables. Given the server's purpose of 'automate security investigations by running analyzers on observables like IPs and URLs', this tool triggers external analysis operations whose effects…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cortex_run_analyzer_by_name Rate-limited

cortex_run_analyzer_by_name 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_by_name": {
      "limits": [
        {
          "counter": "cortex_run_analyzer_by_name_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_by_name

What does the cortex_run_analyzer_by_name tool do? +

Run an analyzer by name instead of ID (convenience wrapper). 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_by_name? +

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

cortex_run_analyzer_by_name 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_by_name? +

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

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

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