AI agents call cortex_list_responder_definitions 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 performs a retrieval operation to enumerate metadata about available responders. It supports filtering but does not create, modify, delete, or execute responders—it only provides visibility into what responders are available. This is a non-destructive read operation with minimal blast radius.
From the tool's definition Tool name contains 'list' and description states it 'List all available responder definitions'; this is a query operation that retrieves and enumerates existing responder definitions without modifying, deleting, or executing any actions.
Attacks that exploit this kind of access
List all available responder definitions (installed but not necessarily enabled). Filter by data type or find responders that require no API keys. 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_list_responder_definitions: 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_list_responder_definitions 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_list_responder_definitions 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_list_responder_definitions. 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_list_responder_definitions 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 →