Critical Risk →

tokens_send_ft

tokens_send_ft

How to control tokens_send_ft ↓

What tokens_send_ft does on NEAR MCP

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

Critical Risk

Why tokens_send_ft needs a policy

The name 'tokens_send_ft' on a NEAR blockchain MCP server almost certainly transfers fungible tokens (FT) between accounts. Sending tokens is a financial operation that moves value on-chain and is irreversible once confirmed. Combined with sibling tools like account_delete_account and account_delete_access_keys suggesting high-privilege operations, misuse could result in permanent loss of funds.

From the tool's definition Tool name 'tokens_send_ft' strongly implies sending fungible tokens on the NEAR blockchain, which constitutes a financial transfer operation. Description is empty, lowering confidence slightly.

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

How to control tokens_send_ft

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_ft:

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

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

  1. Create a free account and register NEAR MCP — 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 tokens_send_ft

What does the tokens_send_ft tool do? +

tokens_send_ft. 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_ft? +

Register the NEAR MCP server in PolicyLayer and add a rule for tokens_send_ft: 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_ft? +

tokens_send_ft 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_ft? +

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

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

tokens_send_ft 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.

Free to start. No card required.

23 NEAR MCP 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.