Critical Risk →

account_delete_account

account_delete_account

How to control account_delete_account ↓

What account_delete_account does on NEAR MCP

AI agents call account_delete_account to permanently remove resources in NEAR MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why account_delete_account needs a policy

Account deletion is a destructive operation that irreversibly removes an account and its associated state from the blockchain. This cannot be reversed. Given the NEAR blockchain context where account actions have permanent financial and data implications, misuse by an AI agent could result in loss of access to funds, permanent account destruction, and inability to recover assets.

From the tool's definition Tool name 'account_delete_account' indicates irreversible deletion of a blockchain account. The empty description prevents confirming exact effects, but the name unambiguously describes account deletion, which cannot be undone on the NEAR blockchain.

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

How to control account_delete_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_delete_account:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "account_delete_account"
  ]
}

account_delete_account disappears from the agent's tool list entirely, and any attempt to call it is denied. 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.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about account_delete_account

What does the account_delete_account tool do? +

account_delete_account. It is categorised as a Destructive tool in the NEAR MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on account_delete_account? +

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

account_delete_account is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit account_delete_account? +

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

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

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

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.