AI agents call cortex_get_job_report to retrieve information from Cortex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves analysis reports, which is a read operation with no side effects or data modification. Severity is medium rather than low because security analysis reports may contain sensitive information about investigated observables (IPs, URLs, threat indicators), and an LLM agent with unconstrained access could exfiltrate intelligence data.
From the tool's definition Tool name 'cortex_get_job_report' and description 'Get the full report of a completed analysis job' indicate retrieval of existing data without modification. The 'get' verb and action of retrieving a report confirm read-only semantics.
Attacks that exploit this kind of access
Get the full report of a completed analysis job. It is categorised as a Read tool in the Cortex MCP Server, which means it retrieves data without modifying state.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_get_job_report: 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_get_job_report is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cortex_get_job_report 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_get_job_report. 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_get_job_report 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 →