send_inbox_message
⛔ DEPRECATED — do not use. The sponsored (relay) inbox send has been removed.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/send-inbox-message.md
What send_inbox_message does on Aibtc
AI agents use send_inbox_message to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why send_inbox_message is rated Medium
Although nominally a Write action (sending a message would create data), the tool is explicitly deprecated and non-functional. The deprecated status significantly reduces severity since the tool cannot actually perform its intended operation. Classified as Write rather than Other because the original intent and naming clearly indicate a message-sending (write) capability, even though it is now inert.
From the tool's definition Tool name 'send_inbox_message' indicates a write operation that creates/sends a message. Description states it is deprecated and no longer functional ('has been removed').
Attacks that exploit this kind of access
The rule that runs send_inbox_message 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, this is the rule to start with:
send_inbox_message stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every send_inbox_message call is checked against it from then on.
Questions about send_inbox_message
⛔ DEPRECATED — do not use. The sponsored (relay) inbox send has been removed. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aibtc MCP server in PolicyLayer and add a rule for send_inbox_message: 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 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_inbox_message 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. 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 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.
This server
Across the catalogue