pillar_direct_send

Send sBTC from your Pillar smart wallet to a recipient.

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/pillar-direct-send.md

WHAT IT DOES

What pillar_direct_send does on Aibtc

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

RISK

Why pillar_direct_send is rated Critical

This tool moves cryptocurrency (sBTC) from a user's wallet to another address, which is a financial transfer operation. Misuse could result in irreversible loss of funds, warranting critical severity.

From the tool's definition Send sBTC from your Pillar smart wallet to a recipient

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pillar_direct_send Approval-gated

Any call to pillar_direct_send 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": {
    "pillar_direct_send": {
      "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 pillar_direct_send call is checked against it from then on.

FAQ

Questions about pillar_direct_send

What does the pillar_direct_send tool do? +

Send sBTC from your Pillar smart wallet to a recipient. 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 pillar_direct_send? +

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

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

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

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

pillar_direct_send 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 358 Aibtc tools → Critical-risk tools on this server →

Across the catalogue

menese_send on Mcp Menesesdk → All critical-risk MCP tools → The MCP Attack Database →

Guides

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