Retrieve all virtual keys in your Portkey organization, including their usage limits, rate limits, and status
AI agents call list_virtual_keys to retrieve information from Portkey MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data about virtual keys without altering state. It is a read-only operation that queries existing data. While virtual keys are sensitive credentials, the tool only enumerates and displays their properties without capability to modify, delete, or execute actions. Misuse would leak information about key configurations but cannot directly compromise systems or move money.
From the tool's definition Tool name 'list_virtual_keys' and description 'Retrieve all virtual keys' indicate a query/retrieval operation with no side effects. The description specifies reading metadata (usage limits, rate limits, status) without modifying or deleting anything.
Attacks that exploit this kind of access
Retrieve all virtual keys in your Portkey organization, including their usage limits, rate limits, and status. It is categorised as a Read tool in the Portkey MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Portkey MCP Server 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 MCP Server. 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 MCP Server MCP server (r-huijts/portkey-admin-mcp-server). 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 →