AI agents call list_api_keys to retrieve information from AnythingLLM 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 because it retrieves data (API keys) without side effects. However, severity is high because API keys are highly sensitive credentials; if an AI agent misuses this tool, it could expose authentication tokens that attackers could use to impersonate users or gain unauthorized access to the AnythingLLM instance.
From the tool's definition Tool name and description indicate it 'List all API keys' — a read-only query operation that retrieves sensitive authentication credentials without modifying them.
Documented attack patterns abuse exactly the kind of access list_api_keys gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AnythingLLM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_api_keys:
{
"version": "1",
"default": "deny",
"tools": {
"list_api_keys": {}
}
}list_api_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.
List all API keys. It is categorised as a Read tool in the AnythingLLM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AnythingLLM 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 AnythingLLM 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 AnythingLLM MCP Server MCP server (raqueljezweb/anythingllm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AnythingLLM MCP Server, 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.
38 AnythingLLM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.