list_virtual_keys
List provider API keys stored as virtual keys in your Portkey org. Use this to find slugs before wiring prompts/configs or auditing limits. Returns total plus name, slug, status, usage limits, rate limits, reset state, and model config.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/list-virtual-keys.md
What list_virtual_keys does on Portkey Admin
AI agents call list_virtual_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_virtual_keys is rated Low
This tool queries and retrieves information about virtual keys (API key metadata) without modifying, executing, or deleting anything. It is a read-only operation. Severity is medium rather than low because the tool exposes metadata about API keys including their names, slugs, and rate/usage limits—sensitive organizational configuration data that could inform an attacker about key management patterns, though the…
From the tool's definition Tool description states 'List provider API keys' and 'Returns total plus name, slug, status, usage limits, rate limits, reset state, and model config.' The verb 'List' and the action of retrieving metadata about stored keys indicates data retrieval with no…
Attacks that exploit this kind of access
The rule that runs list_virtual_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_virtual_keys, this is the rule to start with:
list_virtual_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_virtual_keys call is checked against it from then on.
Questions about list_virtual_keys
List provider API keys stored as virtual keys in your Portkey org. Use this to find slugs before wiring prompts/configs or auditing limits. Returns total plus name, slug, status, usage limits, rate limits, reset state, and model config. 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_virtual_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_virtual_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_virtual_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_virtual_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_virtual_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