Critical Risk →

mnee_sendMnee

Send MNEE tokens to a specified address

How to control mnee_sendMnee ↓

What mnee_sendMnee does on Bitcoin SV MCP Server

AI agents use mnee_sendMnee to commit financial operations through Bitcoin SV MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Why mnee_sendMnee needs a policy

This tool transfers MNEE tokens (a financial asset on the BSV blockchain) to another address. Moving cryptocurrency tokens constitutes a financial transaction that is irreversible once confirmed on-chain. Misuse could result in permanent loss of funds, warranting critical severity.

From the tool's definition Send MNEE tokens to a specified address

Documented attack patterns abuse exactly the kind of access mnee_sendMnee gives an agent:

How to control mnee_sendMnee

PolicyLayer is an MCP gateway — it sits between your AI agents and Bitcoin SV MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mnee_sendMnee:

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

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

  1. Create a free account and register Bitcoin SV MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about mnee_sendMnee

What does the mnee_sendMnee tool do? +

Send MNEE tokens to a specified address. It is categorised as a Financial tool in the Bitcoin SV MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on mnee_sendMnee? +

Register the Bitcoin SV MCP Server MCP server in PolicyLayer and add a rule for mnee_sendMnee: 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 Bitcoin SV MCP Server. Nothing to install.

What risk level is mnee_sendMnee? +

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

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

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

mnee_sendMnee is provided by the Bitcoin SV MCP Server MCP server (b-open-io/bsv-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bitcoin SV MCP Server tool call.

Start from Bitcoin SV MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

80 Bitcoin SV MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.