AI agents call account_delete_access_keys 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.
Deleting access keys is a destructive action that cannot be undone. Once deleted, these keys are permanently removed and cannot be recovered, preventing any authentication with those keys. This falls under the Destructive category rather than Write (which is reversible). While the description is empty, the function name provides clear evidence of destructive intent.
From the tool's definition Tool name is 'account_delete_access_keys' which explicitly indicates deletion of access keys. The action is irreversible and removes authentication credentials from a blockchain account.
Documented attack patterns abuse exactly the kind of access account_delete_access_keys 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 account_delete_access_keys:
{
"version": "1",
"default": "deny",
"hide": [
"account_delete_access_keys"
]
}account_delete_access_keys 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.
account_delete_access_keys. 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 account_delete_access_keys: 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.
account_delete_access_keys 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 account_delete_access_keys 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 account_delete_access_keys. 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.
account_delete_access_keys 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.