Clear all continuous wheel writes.
AI agents call clear_continuous to permanently remove resources in GTAV-CLAUDE-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing all continuous wheel writes is an irreversible bulk deletion of active state (the ongoing write operations are terminated and cannot be recovered). This maps to Destructive rather than Write because it's a mass-clear/purge action. Severity is medium since it affects in-game memory writes within a sandboxed game environment, but misuse could disrupt active game state or automation sequences.
From the tool's definition 'Clear all continuous wheel writes' — permanently removes/clears all ongoing continuous wheel write operations
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all continuous wheel writes. It is categorised as a Destructive tool in the GTAV-CLAUDE-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GTAV-CLAUDE- MCP server in PolicyLayer and add a rule for clear_continuous: 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 GTAV-CLAUDE-MCP. Nothing to install.
clear_continuous 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 clear_continuous 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 clear_continuous. 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.
clear_continuous is provided by the GTAV-CLAUDE- MCP server (tabbedscamper/gtav-claude-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 →