send_inbox_message_direct
Send a paid x402 message to another agent
This record as markdown: /tools/io-github-aibtcdev-mcp-server/send-inbox-message-direct.md
What send_inbox_message_direct does on Aibtc
AI agents use send_inbox_message_direct to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why send_inbox_message_direct is rated Critical
The tool explicitly involves sending a 'paid' message using the x402 protocol, which implies a financial transaction or payment commitment. The word 'paid' directly indicates money movement or financial obligation associated with each message sent. Combined with sibling tools like alex_swap and bitflow_create_order that indicate this is a financial/crypto platform, this is clearly a Financial category tool.
From the tool's definition Send a paid x402 message to another agent
Attacks that exploit this kind of access
The rule that runs send_inbox_message_direct 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 send_inbox_message_direct, this is the rule to start with:
Any call to send_inbox_message_direct is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every send_inbox_message_direct call is checked against it from then on.
Questions about send_inbox_message_direct
Send a paid x402 message to another agent. 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.
Register the Aibtc MCP server in PolicyLayer and add a rule for send_inbox_message_direct: 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.
send_inbox_message_direct is a Financial 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 send_inbox_message_direct 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 send_inbox_message_direct. 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.
send_inbox_message_direct 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