Purpose: List API keys for the configured RawTree database. NOT for: Creating or revoking credentials. Use create-api-key or delete-api-key for those workflows. Returns: API key names, IDs, API key hints, permissions, database, organization, and creation dates. Auth: Uses GET /v1/keys and require...
AI agents call list-api-keys to retrieve information from RawTree MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read operation that retrieves metadata about API keys without modifying them. However, the sensitive nature of API key information elevates severity to medium—an attacker could use this to discover what credentials exist and their permissions, potentially informing further attacks.
From the tool's definition Tool description states 'List API keys' and 'Returns: API key names, IDs, API key hints, permissions, database, organization, and creation dates.' Uses GET /v1/keys which is a read operation. Explicitly states it is 'NOT for: Creating or revoking credentials.'
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Purpose: List API keys for the configured RawTree database. NOT for: Creating or revoking credentials. Use create-api-key or delete-api-key for those workflows. Returns: API key names, IDs, API key hints, permissions, database, organization, and creation dates. Auth: Uses GET /v1/keys and requires an admin database API key. When to use: - User asks what API keys exist - You need the key ID before revoking a key - You need to audit permissions for a database. It is categorised as a Read tool in the RawTree MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RawTree MCP Server 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 RawTree MCP Server. 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 RawTree MCP Server MCP server (rawtreedb/rawtree-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 →