atstake_merge_complete_set
Hand back a matched pair of shares and take the sBTC out: burns
This record as markdown: /tools/io-github-aibtcdev-mcp-server/atstake-merge-complete-set.md
What atstake_merge_complete_set does on Aibtc
AI agents call atstake_merge_complete_set to permanently remove resources in Aibtc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why atstake_merge_complete_set is rated Critical
Burning shares is irreversible destruction of on-chain assets.
From the tool's definition burns, hand back matched pair, take sBTC out
Attacks that exploit this kind of access
The rule that runs atstake_merge_complete_set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For atstake_merge_complete_set, this is the rule to start with:
atstake_merge_complete_set 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 Aibtc, apply this rule, and every atstake_merge_complete_set call is checked against it from then on.
Questions about atstake_merge_complete_set
Hand back a matched pair of shares and take the sBTC out: burns. It is categorised as a Destructive tool in the Aibtc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for atstake_merge_complete_set: 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 Aibtc. Nothing to install.
atstake_merge_complete_set 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 atstake_merge_complete_set 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 atstake_merge_complete_set. 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.
atstake_merge_complete_set is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
Across the catalogue