New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

q402_clear_delegation

Clear the EIP-7702 delegation on a Q402 chain for the configured wallet.

SERVERQ402 Mcp SOURCE@quackai/q402-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitgett-q402-mcp/q402-clear-delegation.md

What q402_clear_delegation does on Q402 Mcp

AI agents call q402_clear_delegation to permanently remove resources in Q402 Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why q402_clear_delegation is rated Critical

This tool permanently modifies blockchain state by clearing EIP-7702 delegation. While not deleting funds, it destroys critical functionality configuration for the wallet's gasless payment capability. The action is irreversible in the sense that the delegation must be re-established from scratch.

From the tool's definition 'Clear the EIP-7702 delegation' — irreversibly removes delegation settings on the configured wallet, preventing future gasless operations dependent on that delegation and cannot be undone without re-delegating.

Questions about q402_clear_delegation

What does the q402_clear_delegation tool do? +

Clear the EIP-7702 delegation on a Q402 chain for the configured wallet. It is categorised as a Destructive tool in the Q402 Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on q402_clear_delegation? +

Register the Q402 MCP server in PolicyLayer and add a rule for q402_clear_delegation: 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 Q402 Mcp. Nothing to install.

What risk level is q402_clear_delegation? +

q402_clear_delegation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit q402_clear_delegation? +

Yes. Add a rate_limit block to the q402_clear_delegation 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.

How do I block q402_clear_delegation completely? +

Set action: deny in the PolicyLayer policy for q402_clear_delegation. 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.

What MCP server provides q402_clear_delegation? +

q402_clear_delegation is provided by the Q402 MCP server (@quackai/q402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Q402, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Q402's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.