List all statuses/stages in a workflow.
AI agents call list_pipeline_workflow_statuses to retrieve information from CATS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates configuration data (pipeline workflow statuses) from the CATS system. The 'list' verb and read-only nature of querying statuses/stages confirm it is a Read operation with no side effects. Risk is low as it only exposes workflow metadata.
From the tool's definition Tool name 'list_pipeline_workflow_statuses' and description 'List all statuses/stages in a workflow' indicate a retrieval operation that queries existing workflow data without modifying or executing actions.
Attacks that exploit this kind of access
List all statuses/stages in a workflow. It is categorised as a Read tool in the CATS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for list_pipeline_workflow_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 CATS MCP Server. Nothing to install.
list_pipeline_workflow_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_workflow_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_workflow_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_workflow_statuses is provided by the CATS MCP Server MCP server (vanman2024/cats-mcp-server). 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 →