run_loop_tick
ONE-CALL value: one Recursive Loop improvement cycle — no demo order. Free 3/day then $0.25/tick. Returns next phase + measurable actions.
This record as markdown: /tools/dev-dualregistry-registry/run-loop-tick.md
What run_loop_tick does on Dual Registry
AI agents invoke run_loop_tick to trigger actions in Dual Registry. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
goals | string | — | |
agent_name | string | Yes | |
listing_id | string | — | |
prior_state | object | — | |
payment_proof | string | — |
Parameters from the server's own tool schema.
Why run_loop_tick is rated High
run_loop_tick triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs run_loop_tick safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dual Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_loop_tick, this is the rule to start with:
run_loop_tick stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dual Registry, apply this rule, and every run_loop_tick call is checked against it from then on.
Questions about run_loop_tick
ONE-CALL value: one Recursive Loop improvement cycle — no demo order. Free 3/day then $0.25/tick. Returns next phase + measurable actions. It is categorised as a Execute tool in the Dual Registry MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
run_loop_tick accepts 5 parameters: goals, agent_name, listing_id, prior_state, payment_proof. Required: agent_name. The full parameter table on this page comes from the server's own tool schema.
Register the Dual Registry MCP server in PolicyLayer and add a rule for run_loop_tick: 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 Dual Registry. Nothing to install.
run_loop_tick 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_tick 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_tick. 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_tick is provided by the Dual Registry MCP server (https://www.dualregistry.dev/api/protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dual Registry, and thousands of servers like it.
Across the catalogue