AI agents invoke pr_invoke to trigger actions in Pr Review. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes an operation that invokes AI agents with side effects on a pull request. Invocation of agents constitutes triggering external operations, making it Execute rather than Write. The incomplete description ('When agent=') suggests parameterized agent selection, which could amplify risk.
From the tool's definition Tool description states 'Invoke AI code review agents on a PR', indicating it triggers external operations (agent invocation) whose effects depend on arguments (which agent, PR details).
Attacks that exploit this kind of access
Invoke AI code review agents on a PR. When agent=. It is categorised as a Execute tool in the Pr Review MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pr Review MCP server in PolicyLayer and add a rule for pr_invoke: 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 Pr Review. Nothing to install.
pr_invoke is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pr_invoke 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_invoke. 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_invoke is provided by the Pr Review MCP server (thebtf/pr-review-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 →