List all API keys for the team with their names, scopes, environments, and last-used timestamps.
AI agents call list_api_keys to retrieve information from NeuronSearchLab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves sensitive information (API key metadata including scopes and environments). While it does not modify or delete data, the exposure of API key scopes and environments could facilitate lateral privilege escalation or unauthorized access if an agent were compromised.
From the tool's definition Tool name 'list_api_keys' and description 'List all API keys for the team' indicate a query/retrieval operation that returns metadata about existing API keys (names, scopes, environments, last-used timestamps) without modifying, deleting, or executing any…
Attacks that exploit this kind of access
List all API keys for the team with their names, scopes, environments, and last-used timestamps. It is categorised as a Read tool in the NeuronSearchLab MCP Server, which means it retrieves data without modifying state.
Register the NeuronSearchLab MCP server in PolicyLayer and add a rule for list_api_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 NeuronSearchLab. Nothing to install.
list_api_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 list_api_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 list_api_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.
list_api_keys is provided by the NeuronSearchLab MCP server (neuronsearchlab/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →