create_virtual_key
Store a provider API key as a virtual key. The raw key is encrypted and only returned at creation time, so save the returned slug and use it in prompts/configs. Optional usage and rate limits apply immediately, and the tool returns the new slug.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/create-virtual-key.md
What create_virtual_key does on Portkey Admin
AI agents use create_virtual_key to create or update resources in Portkey Admin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Portkey Admin environment.
Why create_virtual_key is rated Medium
This tool creates new virtual keys and stores sensitive credentials. It is a Write operation because it creates and persists data reversibly. Severity is high because misuse could store attacker-controlled API credentials that could be used to access external services, compromise the system's integration layer, or enable privilege escalation through stolen provider keys.
From the tool's definition Tool description states: 'Store a provider API key as a virtual key' and 'the tool returns the new slug'. This creates and persists new data (encrypted API key storage).
Attacks that exploit this kind of access
The rule that runs create_virtual_key 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 create_virtual_key, this is the rule to start with:
create_virtual_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_virtual_key call is checked against it from then on.
Questions about create_virtual_key
Store a provider API key as a virtual key. The raw key is encrypted and only returned at creation time, so save the returned slug and use it in prompts/configs. Optional usage and rate limits apply immediately, and the tool returns the new slug. It is categorised as a Write tool in the Portkey Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for create_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.
create_virtual_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue