AI agents call list_pipeline_statuses to retrieve information from Keycrm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation (list/fetch) on pipeline metadata. It retrieves stage information for display or reference purposes only, with no side effects, data modification, or external action execution. The low severity reflects minimal blast radius—an AI agent misusing this tool would only retrieve data it should not see, not modify or delete anything.
From the tool's definition Tool name 'list_pipeline_statuses' and description 'List all stages for a specific pipeline with their IDs and names' indicate a retrieval operation that queries and returns existing pipeline stage data without modification.
Attacks that exploit this kind of access
List all stages for a specific pipeline with their IDs and names. It is categorised as a Read tool in the Keycrm MCP Server, which means it retrieves data without modifying state.
Register the Keycrm MCP server in PolicyLayer and add a rule for list_pipeline_statuses: 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 Keycrm. Nothing to install.
list_pipeline_statuses 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 list_pipeline_statuses 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 list_pipeline_statuses. 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.
list_pipeline_statuses is provided by the Keycrm MCP server (ivanklymenko/keycrm-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 →