Call this when the error you were working on is FIXED — the build passes, the test passes, or the runtime error is gone. This resets all loop tracking counters for the session so the next error starts with a clean slate. IMPORTANT: Always call this after resolving an error, especially one you wer...
AI agents use resolve_loop to create or update resources in Unloop MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unloop MCP environment.
resolve_loop modifies session state by resetting counters and clearing attempt history. This is a reversible, non-destructive write operation that updates metadata about the AI's coding attempts. It has no side effects on actual code, builds, or external systems — only on the tool's internal tracking state.
From the tool's definition The tool 'resets all loop tracking counters for the session' and clears 'stale attempt history' — these are state modifications that update internal tracking records.
Attacks that exploit this kind of access
Call this when the error you were working on is FIXED — the build passes, the test passes, or the runtime error is gone. This resets all loop tracking counters for the session so the next error starts with a clean slate. IMPORTANT: Always call this after resolving an error, especially one you were looping on. If you skip this, the next unrelated error may trigger false loop alerts because the stale attempt history is still active. It is categorised as a Write tool in the Unloop MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unloop MCP server in PolicyLayer and add a rule for resolve_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 Unloop MCP. Nothing to install.
resolve_loop 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 resolve_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 resolve_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.
resolve_loop is provided by the Unloop MCP server (protonese3/unloop-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 →