List all NEAR accounts and their keypairs in the local keystore by network.
AI agents call system_list_local_keypairs 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.
The tool retrieves and enumerates sensitive data (keypairs and account information) from local storage but does not modify, delete, or execute any operations. It is a Read operation. Severity is high because keypairs are highly sensitive cryptographic material—exposure of this list could enable an attacker to identify which accounts exist locally and target them for further compromise.
From the tool's definition Tool name contains 'list' and description states 'List all NEAR accounts and their keypairs in the local keystore by network.' This is a retrieval operation with no side effects.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access system_list_local_keypairs 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_list_local_keypairs:
{
"version": "1",
"default": "deny",
"tools": {
"system_list_local_keypairs": {}
}
}system_list_local_keypairs 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.
List all NEAR accounts and their keypairs in the local keystore by network. 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 system_list_local_keypairs: 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_list_local_keypairs 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 system_list_local_keypairs 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_list_local_keypairs. 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_list_local_keypairs 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.