atstake_transfer_shares

Send shares of one side to another principal.\n\n

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity verified Pull the record →

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

WHAT IT DOES

What atstake_transfer_shares does on Aibtc

AI agents use atstake_transfer_shares to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why atstake_transfer_shares is rated Critical

Tool transfers ownership of financial assets (shares) between principals, committing financial obligations.

From the tool's definition Send shares of one side to another principal

Attacks that exploit this kind of access

RECOMMENDED RULE

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

atstake_transfer_shares Approval-gated

Any call to atstake_transfer_shares is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "atstake_transfer_shares": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about atstake_transfer_shares

What does the atstake_transfer_shares tool do? +

Send shares of one side to another principal.\n\n. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on atstake_transfer_shares? +

Register the Aibtc MCP server in PolicyLayer and add a rule for atstake_transfer_shares: 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_transfer_shares? +

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

Can I rate-limit atstake_transfer_shares? +

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

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

atstake_transfer_shares 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

bridge_transfer on 0xaibridge →transfer_sites on A3plus →abs_zalo_transfer_owner on Abs Zalo Bot → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →