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.
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | The actual provider API key to store |
name | string | Yes | Display name for the virtual key |
note | string | — | Optional note or description for this key |
provider | string | Yes | Provider slug (e.g., 'openai', 'anthropic', 'azure-openai', 'google') |
api_version | string | — | API version (for Azure OpenAI) |
credit_limit | number | — | Maximum usage cost threshold |
workspace_id | string | — | Workspace ID to create the key in |
resource_name | string | — | Resource name (for Azure OpenAI) |
rate_limit_rpm | number | — | Requests per minute limit |
alert_threshold | number | — | Percentage of credit_limit at which to send alert emails (0-100) |
deployment_name | string | — | Deployment name (for Azure OpenAI) |
Parameters from the server's own tool schema.
An AI agent can call create_virtual_key faster than any human can review — one bad instruction and it creates or modifies resources in Portkey Admin by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
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.
create_virtual_key accepts 11 parameters: key, name, note, provider, api_version, credit_limit, workspace_id, resource_name, rate_limit_rpm, alert_threshold, deployment_name. Required: key, name, provider. The full parameter table on this page comes from the server's own tool schema.
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.