View recent pipeline runs and their results.
AI agents call cortex_pipeline_history to retrieve information from Cortex MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data about pipeline execution results. It has no side effects, does not modify any state, execute code, delete data, or affect financial systems. It is a simple read operation that queries and displays information about past runs.
From the tool's definition Tool name indicates 'View' operation and description states 'View recent pipeline runs and their results' - purely a retrieval/query operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
View recent pipeline runs and their results. It is categorised as a Read tool in the Cortex MCP MCP Server, which means it retrieves data without modifying state.
Register the Cortex MCP server in PolicyLayer and add a rule for cortex_pipeline_history: 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_pipeline_history 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_pipeline_history 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_pipeline_history. 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_pipeline_history 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 →