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

prepare_rocketpool_unstake

Build an unsigned Rocket Pool unstake transaction (rETH.burn(uint256), redeems rETH for ETH from on-protocol collateral). No approval needed — burn operates on caller's balance. Preflights wallet rETH balance and rETH contract collateral; if collateral is insufficient, refuses with a hint to unwi...

SERVERVaultPilot MCP SOURCEvaultpilot-mcp
High RISK CLASS
Category Execute
Parameters 22 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-rocketpool-unstake.md

What prepare_rocketpool_unstake does on VaultPilot MCP

AI agents invoke prepare_rocketpool_unstake to trigger actions in VaultPilot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

ParameterTypeRequiredDescription
wallet string Yes
amountReth string Yes Human-readable rETH amount to burn for ETH, NOT raw wei. Example: "0.5" for 0.5 rETH (18 decimals). Burning requires sufficient on-protocol ETH collateral (rETH

Parameters from the server's own tool schema.

Why prepare_rocketpool_unstake is rated High

This tool constructs transactions that execute external smart contract operations (rETH burning/redeeming), making it Execute rather than Write. It is not Financial because it does not itself move money—it builds an unsigned transaction for later submission. It is not Destructive because burning rETH is reversible via the suggested alternative (Uniswap V3 pool swap).

From the tool's definition Builds an unsigned Rocket Pool unstake transaction that burns rETH and redeems ETH from on-protocol collateral. The tool triggers an external protocol operation (rETH.burn) whose financial effects depend on the amount argument and current protocol state.

Questions about prepare_rocketpool_unstake

What does the prepare_rocketpool_unstake tool do? +

Build an unsigned Rocket Pool unstake transaction (rETH.burn(uint256), redeems rETH for ETH from on-protocol collateral). No approval needed — burn operates on caller's balance. Preflights wallet rETH balance and rETH contract collateral; if collateral is insufficient, refuses with a hint to unwind via the rETH/ETH Uniswap V3 pool instead. It is categorised as a Execute tool in the VaultPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does prepare_rocketpool_unstake accept? +

prepare_rocketpool_unstake accepts 2 parameters: wallet, amountReth. Required: wallet, amountReth. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on prepare_rocketpool_unstake? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_rocketpool_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 VaultPilot MCP. Nothing to install.

What risk level is prepare_rocketpool_unstake? +

prepare_rocketpool_unstake is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit prepare_rocketpool_unstake? +

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

How do I block prepare_rocketpool_unstake completely? +

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

What MCP server provides prepare_rocketpool_unstake? +

prepare_rocketpool_unstake is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on VaultPilot, 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 VaultPilot'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.