This record as markdown: /tools/codeswhat-portkey-admin-mcp/update-virtual-key.md
What update_virtual_key does on Portkey Admin
AI agents use update_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 update_virtual_key is rated Medium
This tool creates or modifies data reversibly (fitting the Write category). While not destructive, updating virtual keys—which are security credentials—poses significant risk if an AI agent misuses it to modify access controls, rotate keys for malicious purposes, or escalate privileges. Severity is high due to the security-critical nature of credential modification in an admin API context.
From the tool's definition Tool name 'update_virtual_key' and description 'Update a virtual key' indicate modification of existing data. Virtual keys in admin/security contexts are credentials or access tokens, making unauthorized updates a high-severity concern.
Attacks that exploit this kind of access
The rule that runs update_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 update_virtual_key, this is the rule to start with:
update_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 update_virtual_key call is checked against it from then on.
Questions about update_virtual_key
Update a virtual key. 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 update_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.
update_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 update_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 update_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.
update_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