This record as markdown: /tools/codeswhat-portkey-admin-mcp/update-mcp-server.md
What update_mcp_server does on Portkey Admin
AI agents use update_mcp_server 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_mcp_server is rated Medium
This tool modifies an MCP server's settings or configuration, which is a reversible change to data. It does not delete resources (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).
From the tool's definition Tool name 'update_mcp_server' and description 'Update an MCP server' indicate modification of existing configuration/data. The word 'update' is a classic Write operation verb.
Attacks that exploit this kind of access
The rule that runs update_mcp_server 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_mcp_server, this is the rule to start with:
update_mcp_server 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_mcp_server call is checked against it from then on.
Questions about update_mcp_server
Update an MCP server. 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_mcp_server: 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_mcp_server 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_mcp_server 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_mcp_server. 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_mcp_server 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