Update an API key's name, description, scopes, defaults, or limits, unlike delete_api_key which revokes it or create_api_key which issues a new one. Changes take effect immediately for downstream callers, type and sub-type stay fixed after creation, and the call returns success without rotating t...
AI agents use update_api_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 |
|---|---|---|---|
id | string | Yes | The UUID of the API key to update |
name | string | — | New display name for the key |
scopes | array | — | New permission scopes for the key |
expires_at | object | — | New expiration date in ISO 8601 format, or null to remove expiration |
description | string | — | New description for the key |
alert_emails | array | — | New email addresses for alerts |
credit_limit | number | — | New credit limit for usage |
rate_limit_rpm | number | — | New rate limit in requests per minute |
alert_threshold | number | — | New alert threshold percentage (0-100) |
default_metadata | object | — | New default metadata key-value pairs |
default_config_id | string | — | New default configuration ID |
Parameters from the server's own tool schema.
An AI agent can call update_api_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
Update an API key's name, description, scopes, defaults, or limits, unlike delete_api_key which revokes it or create_api_key which issues a new one. Changes take effect immediately for downstream callers, type and sub-type stay fixed after creation, and the call returns success without rotating the secret. 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.
update_api_key accepts 11 parameters: id, name, scopes, expires_at, description, alert_emails, credit_limit, rate_limit_rpm, alert_threshold, default_metadata, default_config_id. Required: id. 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 update_api_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.
update_api_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 update_api_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 update_api_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.
update_api_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.