account_list_access_keys
AI agents call account_list_access_keys to retrieve information from NEAR MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates access keys for an account on the NEAR blockchain. The lack of description reduces confidence slightly, but the imperative verb 'list' and the context of sibling tools (which include creation, deletion, and signing operations) strongly suggest this is a query operation. Listing access keys does not modify state, execute code, or cause irreversible changes.
From the tool's definition Tool name 'account_list_access_keys' indicates listing/querying access keys associated with an account. The 'list' verb is characteristic of read operations that retrieve information without modification.
Documented attack patterns abuse exactly the kind of access account_list_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_list_access_keys:
{
"version": "1",
"default": "deny",
"tools": {
"account_list_access_keys": {}
}
}account_list_access_keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
account_list_access_keys. It is categorised as a Read tool in the NEAR MCP MCP Server, which means it retrieves data without modifying state.
Register the NEAR MCP server in PolicyLayer and add a rule for account_list_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_list_access_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the account_list_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_list_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_list_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.