This record as markdown: /tools/io-github-bitgett-q402-mcp/q402-unstake.md
What q402_unstake does on Q402 Mcp
AI agents use q402_unstake to commit financial operations through Q402 Mcp, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why q402_unstake is rated Critical
Unstaking moves staked funds back to the agent wallet, which is a financial operation that alters the state of staked assets. Given this server handles gasless payments across 10 EVM chains and CCIP bridge, unstaking directly affects financial holdings. The description explicitly states 'MOVES FUNDS', confirming irreversible financial movement.
From the tool's definition WRITE - MOVES FUNDS. Unstakes the Agent Wallet
Attacks that exploit this kind of access
The rule that runs q402_unstake safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Q402 Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For q402_unstake, this is the rule to start with:
Any call to q402_unstake is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Q402 Mcp, apply this rule, and every q402_unstake call is checked against it from then on.
Questions about q402_unstake
WRITE - MOVES FUNDS. Unstakes the Agent Wallet. It is categorised as a Financial tool in the Q402 Mcp MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Q402 MCP server in PolicyLayer and add a rule for q402_unstake: 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.
q402_unstake is a Financial 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 q402_unstake 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 q402_unstake. 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.
q402_unstake 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.
Across the catalogue