High Risk →

contract_call_raw_function

contract_call_raw_function

How to control contract_call_raw_function ↓

What contract_call_raw_function does on NEAR MCP

AI agents invoke contract_call_raw_function to trigger actions in NEAR MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why contract_call_raw_function needs a policy

The name strongly implies executing a raw smart contract function call on the NEAR blockchain. Contract calls can have wide-ranging effects including state changes, token transfers, and other on-chain operations. The 'raw' qualifier suggests arbitrary/unconstrained execution.

From the tool's definition Tool name: 'contract_call_raw_function' — 'call' suggests executing a smart contract function on the NEAR blockchain

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

How to control contract_call_raw_function

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "contract_call_raw_function": {
      "limits": [
        {
          "counter": "contract_call_raw_function_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

contract_call_raw_function stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about contract_call_raw_function

What does the contract_call_raw_function tool do? +

contract_call_raw_function. It is categorised as a Execute tool in the NEAR MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on contract_call_raw_function? +

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

contract_call_raw_function is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit contract_call_raw_function? +

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

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

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