tokens_send_near

THE RISK

Critical Risk

Why tokens_send_near needs a policy

The tool name explicitly indicates sending NEAR tokens, which constitutes a financial transaction moving cryptocurrency. Even with an empty description, the combination of 'tokens', 'send', and 'NEAR' (the blockchain's native currency) strongly implies a financial transfer operation. Misuse by an AI agent could result in irreversible loss of funds, warranting critical severity.

From the tool's definition Tool name 'tokens_send_near' on a NEAR blockchain MCP server; 'send' implies transferring NEAR tokens (cryptocurrency) to another account.

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

POLICY

How to control tokens_send_near

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

policy.json

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

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

Create a free account and register NEAR MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

GATE THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More NEAR MCP tools

Financial ref_finance_execute_swap ref_finance_execute_swap Financial tokens_send_ft tokens_send_ft Destructive account_delete_access_keys account_delete_access_keys Destructive account_delete_account account_delete_account Destructive system_remove_local_account system_remove_local_account Execute account_sign_data account_sign_data Execute contract_call_raw_function contract_call_raw_function Write account_add_access_key account_add_access_key

All 23 NEAR MCP tools →

Financial tools on other servers

0xarchive web3_subscribe Math MCP Server financial_calculator MCP Kling generate_video MCP Uber Server uber_request_ride

Go deeper

Critical-risk tools in NEAR MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Human-in-the-loop → When a tool call should wait for a person — and when policy can decide alone.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
How to Add Spending Controls to Any MCP Agent →
Rate Limiting MCP Tool Calls: A Practical Guide →

FAQ

Questions about tokens_send_near

What does the tokens_send_near tool do? +

tokens_send_near. It is categorised as a Financial tool in the NEAR MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on tokens_send_near? +

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

What risk level is tokens_send_near? +

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

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

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

tokens_send_near is provided by the NEAR MCP server (nearai/near-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NEAR MCP tool call.

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

CHECK YOUR STACK →