AI agents invoke run_loop to trigger actions in Proxima. 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 triggers repeated execution of AI operations in a loop with conditional termination (convergence or maxTurns). While it does not permanently delete data (not Destructive) or move money (not Financial), it performs autonomous iterative operations whose outcomes depend on arguments and model behavior.
From the tool's definition The tool 'run_loop' iterates a task through multiple AI models in a generate-review-improve cycle controlled by maxTurns parameter.
Attacks that exploit this kind of access
Iterate ONE task: generate → another AI reviews → improve, until it converges or hits maxTurns. Use to refine a single output; use run_workflow for distinct sequential steps. It is categorised as a Execute tool in the Proxima MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxima MCP server in PolicyLayer and add a rule for run_loop: 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 Proxima. Nothing to install.
run_loop 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 run_loop 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 run_loop. 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.
run_loop is provided by the Proxima MCP server (zen4-bit/proxima). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
run_loop is one line of Proxima's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →