Get PR mergeability and state; polls until not UNKNOWN if requested.
AI agents call pr.status to retrieve information from Promethean OS MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves PR metadata (mergeability and state) through polling. It has no side effects, does not modify data, and does not execute code or perform financial transactions. It is a pure read operation on GitHub PR state.
From the tool's definition Tool name 'pr.status' and description 'Get PR mergeability and state; polls until not UNKNOWN if requested' indicate a query operation that retrieves information about pull request status without modifying any data.
Attacks that exploit this kind of access
Get PR mergeability and state; polls until not UNKNOWN if requested. It is categorised as a Read tool in the Promethean OS MCP MCP Server, which means it retrieves data without modifying state.
Register the Promethean OS MCP server in PolicyLayer and add a rule for pr.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 Promethean OS MCP. Nothing to install.
pr.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 pr.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 pr.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.
pr.status is provided by the Promethean OS MCP server (octave-commons/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 →