list_api_keys
List Portkey API keys for auditing access, scopes, defaults, limits, and expiration. Use this for API keys only; use list_virtual_keys for provider keys. Returns total plus id, type, status, workspace/user scope, limits, defaults, alert emails, and creation mode.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/list-api-keys.md
What list_api_keys does on Portkey Admin
AI agents call list_api_keys to retrieve information from Portkey Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_api_keys is rated Low
This tool retrieves and queries API key metadata for auditing purposes without modifying, creating, or deleting any data. It falls squarely into the Read category. Severity is elevated to medium because exposing API key details (scope, limits, creation mode, alert emails, status) could enable privilege escalation or circumvention of access controls if an AI agent misuses this information to identify high-value or…
From the tool's definition Tool description states 'List Portkey API keys for auditing access' and 'Returns total plus id, type, status, workspace/user scope, limits, defaults, alert emails, and creation mode.' The verb 'List' and action of retrieving metadata about API keys indicates…
Attacks that exploit this kind of access
The rule that runs list_api_keys safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_api_keys, this is the rule to start with:
list_api_keys is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every list_api_keys call is checked against it from then on.
Questions about list_api_keys
List Portkey API keys for auditing access, scopes, defaults, limits, and expiration. Use this for API keys only; use list_virtual_keys for provider keys. Returns total plus id, type, status, workspace/user scope, limits, defaults, alert emails, and creation mode. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.
Register the Portkey Admin 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 Portkey Admin. 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 Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue