update_virtual_key

Update a virtual key

SERVERPortkey Admin SOURCEcodeswhat/portkey-admin-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about update_virtual_key

What does the update_virtual_key tool do? +

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.

How do I enforce a policy on update_virtual_key? +

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.

What risk level is update_virtual_key? +

update_virtual_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_virtual_key? +

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.

How do I block update_virtual_key completely? +

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.

What MCP server provides update_virtual_key? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Portkey Admin's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.