account_export_account

THE RISK

Low Risk

Why account_export_account needs a policy

The description is empty, so the exact behavior is unknown. Based on the name, 'export account' on a blockchain context likely involves exporting private keys or seed phrases, which could be a Read operation but carries high risk if credentials are exposed. Without a description, confidence is low, but the name suggests credential/key material retrieval rather than a standard data read, write, or destructive action.

From the tool's definition Tool name is 'account_export_account'; description is empty or uninformative.

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

POLICY

How to control account_export_account

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "account_export_account": {
      "limits": [
        {
          "counter": "account_export_account_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

account_export_account gets a rate cap, and everything else on the server is denied unless you say otherwise.

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.

SET A RULE FOR 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 Financial tokens_send_near tokens_send_near 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

All 23 NEAR MCP tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about account_export_account

What does the account_export_account tool do? +

account_export_account. It is categorised as a Other tool in the NEAR MCP MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on account_export_account? +

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

account_export_account is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit account_export_account? +

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

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

account_export_account 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 →