Add PR to merge queue.
AI agents use pr.enqueue to create or update resources in Promethean OS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Promethean OS MCP environment.
This tool modifies repository state by placing a PR into a merge queue, which triggers an automated merge workflow. While the action itself is reversible (PRs can be dequeued), it commits a change that will cause downstream effects (automated merging). The severity is 'high' because misuse could result in unintended code deployments to production or main branches.
From the tool's definition The tool 'pr.enqueue' is described as 'Add PR to merge queue,' which involves modifying the state of a pull request by enqueuing it for merging—a reversible state change in a version control system.
Attacks that exploit this kind of access
Add PR to merge queue. It is categorised as a Write tool in the Promethean OS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Promethean OS MCP server in PolicyLayer and add a rule for pr.enqueue: 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.enqueue is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pr.enqueue 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.enqueue. 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.enqueue 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 →