menese_send
Send native tokens on any supported blockchain. Supports 19 chains: Ethereum, Polygon, Arbitrum, Base, Optimism, BNB, Bitcoin, Solana, ICP, SUI, TON, XRP, Litecoin, Cardano, Tron, Aptos, NEAR, CloakCoin, Thorchain.
This record as markdown: /tools/aboodtt404-mcp-menese-sdk/menese-send.md
What menese_send does on Mcp Menesesdk
AI agents use menese_send to commit financial operations through Mcp Menesesdk, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why menese_send is rated Critical
This tool moves cryptocurrency (native tokens) from one address to another on supported blockchains. Sending tokens is an irreversible financial transaction that directly moves monetary value.
From the tool's definition "Send native tokens on any supported blockchain" — transfers cryptocurrency assets across 19 chains including Bitcoin, Ethereum, Solana, and others.
Attacks that exploit this kind of access
The rule that runs menese_send safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Menesesdk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For menese_send, this is the rule to start with:
Any call to menese_send is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Menesesdk, apply this rule, and every menese_send call is checked against it from then on.
Questions about menese_send
Send native tokens on any supported blockchain. Supports 19 chains: Ethereum, Polygon, Arbitrum, Base, Optimism, BNB, Bitcoin, Solana, ICP, SUI, TON, XRP, Litecoin, Cardano, Tron, Aptos, NEAR, CloakCoin, Thorchain. It is categorised as a Financial tool in the Mcp Menesesdk MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Mcp Menesesdk MCP server in PolicyLayer and add a rule for menese_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 Mcp Menesesdk. Nothing to install.
menese_send 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 menese_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.
Set action: deny in the PolicyLayer policy for menese_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.
menese_send is provided by the Mcp Menesesdk MCP server (aboodtt404/mcp-menese-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Menesesdk, and thousands of servers like it.
Across the catalogue