atstake_cancel_bid

Withdraw a resting bid and get the unfilled escrow back.\n\n

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/atstake-cancel-bid.md

WHAT IT DOES

What atstake_cancel_bid does on Aibtc

AI agents call atstake_cancel_bid 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.

RISK

Why atstake_cancel_bid is rated Critical

Cancels an existing financial bid, irreversibly terminating the commitment and returning escrowed funds.

From the tool's definition Withdraw a resting bid and get the unfilled escrow back.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs atstake_cancel_bid 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_cancel_bid, this is the rule to start with:

atstake_cancel_bid Hidden

atstake_cancel_bid is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "atstake_cancel_bid"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every atstake_cancel_bid call is checked against it from then on.

FAQ

Questions about atstake_cancel_bid

What does the atstake_cancel_bid tool do? +

Withdraw a resting bid and get the unfilled escrow back.\n\n. 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.

How do I enforce a policy on atstake_cancel_bid? +

Register the Aibtc MCP server in PolicyLayer and add a rule for atstake_cancel_bid: 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.

What risk level is atstake_cancel_bid? +

atstake_cancel_bid 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 atstake_cancel_bid? +

Yes. Add a rate_limit block to the atstake_cancel_bid 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 atstake_cancel_bid completely? +

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

atstake_cancel_bid 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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 366 Aibtc tools → Critical-risk tools on this server →

Across the catalogue

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →