Upgrade the Morpheus agent on a server to the latest version.
AI agents invoke upgrade_server_agent to trigger actions in Morpheus MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Upgrading an agent involves executing an installation/update process on a remote server. This is an Execute-category action as it triggers an external operation with effects dependent on the target server. It is not purely Write (data modification) nor Destructive (not irreversible deletion), but it does execute a software change on infrastructure.
From the tool's definition 'Upgrade the Morpheus agent on a server to the latest version' — triggers an agent software upgrade operation on a remote server
Attacks that exploit this kind of access
Upgrade the Morpheus agent on a server to the latest version. It is categorised as a Execute tool in the Morpheus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for upgrade_server_agent: 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 Morpheus MCP Server. Nothing to install.
upgrade_server_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the upgrade_server_agent 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 upgrade_server_agent. 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.
upgrade_server_agent is provided by the Morpheus MCP Server MCP server (nixndme/morpheus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →