collab_cursor_reset
Append an auditable reset reason and CAS the cursor to an exact valid anchor; ordinary polling never resets automatically.
This record as markdown: /tools/dev-agenttool-agenttool/collab-cursor-reset.md
What collab_cursor_reset does on Agenttool
AI agents call collab_cursor_reset to permanently remove resources in Agenttool, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why collab_cursor_reset is rated Critical
An AI agent that decides to call collab_cursor_reset doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Agenttool is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs collab_cursor_reset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agenttool, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For collab_cursor_reset, this is the rule to start with:
collab_cursor_reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Agenttool, apply this rule, and every collab_cursor_reset call is checked against it from then on.
Questions about collab_cursor_reset
Append an auditable reset reason and CAS the cursor to an exact valid anchor; ordinary polling never resets automatically. It is categorised as a Destructive tool in the Agenttool MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agenttool MCP server in PolicyLayer and add a rule for collab_cursor_reset: 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 Agenttool. Nothing to install.
collab_cursor_reset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the collab_cursor_reset 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 collab_cursor_reset. 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.
collab_cursor_reset is provided by the Agenttool MCP server (https://api.agenttool.dev/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agenttool, and thousands of servers like it.
Across the catalogue