Get the current status of an issue in the pipeline
AI agents call get_pipeline_status to retrieve information from Chiro ERP - Issue Pipeline Orchestrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pipeline status information without side effects. It is a simple query operation (get/fetch) that does not create, modify, execute, delete, or move money. The context that it operates within an orchestrator automating GitHub workflows does not change the nature of this individual tool, which is purely informational.
From the tool's definition Tool name 'get_pipeline_status' and description 'Get the current status of an issue in the pipeline' indicate a read-only query operation that retrieves status information without modifying or executing any workflows.
Attacks that exploit this kind of access
Get the current status of an issue in the pipeline. It is categorised as a Read tool in the Chiro ERP - Issue Pipeline Orchestrator MCP Server, which means it retrieves data without modifying state.
Register the Chiro ERP - Issue Pipeline Orchestrator MCP server in PolicyLayer and add a rule for get_pipeline_status: 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 Chiro ERP - Issue Pipeline Orchestrator. Nothing to install.
get_pipeline_status 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 get_pipeline_status 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 get_pipeline_status. 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.
get_pipeline_status is provided by the Chiro ERP - Issue Pipeline Orchestrator MCP server (olwalgeorge2/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 →