get_virtual_key

Fetch one virtual key by slug, including metadata, a masked secret, limits, status, and model config. Use this before updating or to inspect the current configuration.

Server Portkey Admin CodesWhat/portkey-admin-mcp
Category Read
Risk class Low
Parameters 11 required

What get_virtual_key does on Portkey Admin

AI agents call get_virtual_key to retrieve information from Portkey Admin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
slug string Yes The unique slug identifier of the virtual key to retrieve

Parameters from the server's own tool schema.

Why get_virtual_key needs a policy

Even though get_virtual_key only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about get_virtual_key

What does the get_virtual_key tool do? +

Fetch one virtual key by slug, including metadata, a masked secret, limits, status, and model config. Use this before updating or to inspect the current configuration. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.

What parameters does get_virtual_key accept? +

get_virtual_key accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_virtual_key? +

Register the Portkey Admin MCP server in PolicyLayer and add a rule for get_virtual_key: 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.

What risk level is get_virtual_key? +

get_virtual_key is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_virtual_key? +

Yes. Add a rate_limit block to the get_virtual_key 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.

How do I block get_virtual_key completely? +

Set action: deny in the PolicyLayer policy for get_virtual_key. 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.

What MCP server provides get_virtual_key? +

get_virtual_key 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.