AI agents call system_remove_local_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.
This tool permanently deletes or removes a local account, which is an irreversible action with severe consequences. An AI agent misusing this could permanently destroy user account data and access. Although the description is empty, the tool name and server context provide clear evidence of destructive intent.
From the tool's definition Tool name 'system_remove_local_account' explicitly indicates removal/deletion of a local account. In blockchain contexts (NEAR), account removal is an irreversible operation that cannot be undone.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access system_remove_local_account gives an agent:
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 system_remove_local_account:
{
"version": "1",
"default": "deny",
"hide": [
"system_remove_local_account"
]
}system_remove_local_account disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
system_remove_local_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.
Register the NEAR MCP server in PolicyLayer and add a rule for system_remove_local_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.
system_remove_local_account is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the system_remove_local_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.
Set action: deny in the PolicyLayer policy for system_remove_local_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.
system_remove_local_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.
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.