AI agents invoke purroxy_run_capability to trigger actions in Purroxy. 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 runs pre-recorded browser automation routines, which constitutes executing external operations whose effects depend on the capability argument passed. While the capabilities are 'recorded' (suggesting some pre-authorization), the tool itself is an Execute primitive that triggers side effects in a browser context.
From the tool's definition Tool description states 'Execute a recorded browser automation capability by name.' The verb 'Execute' directly indicates code/automation execution.
Attacks that exploit this kind of access
Execute a recorded browser automation capability by name. It is categorised as a Execute tool in the Purroxy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Purroxy MCP server in PolicyLayer and add a rule for purroxy_run_capability: 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 Purroxy. Nothing to install.
purroxy_run_capability 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 purroxy_run_capability 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 purroxy_run_capability. 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.
purroxy_run_capability is provided by the Purroxy MCP server (kuvopllc/purroxy2). 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 →