account_add_access_key
AI agents use account_add_access_key to create or update resources in NEAR MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NEAR MCP environment.
This tool adds access keys to a blockchain account. Access keys are credentials that enable transactions and operations on the account. While reversible (keys can be deleted via 'account_delete_access_keys'), adding a key is a write operation that modifies account state and permissions. The description is empty, which lowers confidence slightly, but the name and context are clear.
From the tool's definition Tool name is 'account_add_access_key' which indicates creation/modification of access credentials. In the context of blockchain account management (NEAR platform), adding access keys is a reversible write operation that creates new authentication credentials.
Documented attack patterns abuse exactly the kind of access account_add_access_key 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_add_access_key:
{
"version": "1",
"default": "deny",
"tools": {
"account_add_access_key": {
"limits": [
{
"counter": "account_add_access_key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}account_add_access_key stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
account_add_access_key. It is categorised as a Write tool in the NEAR MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the NEAR MCP server in PolicyLayer and add a rule for account_add_access_key: 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_add_access_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the account_add_access_key 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_add_access_key. 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_add_access_key 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.