install_server_agent · Morpheus MCP Server MCP

WHAT IT DOES

What install_server_agent does on Morpheus MCP Server

AI agents invoke install_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.

WHY IT NEEDS A POLICY

Why install_server_agent needs a policy

Installing an agent on a server is an Execute-category action: it runs an installation process on a remote system, modifying its software state. This is not merely a write of data but an active execution of code/operations on infrastructure. Misuse could install agents on unintended servers, compromise security posture, or disrupt running workloads, warranting high severity.

From the tool's definition "Install the Morpheus agent on a server" — installs software on a remote server, triggering an external operation that modifies the server's software environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_server_agent Rate-limited

install_server_agent stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "install_server_agent": {
      "limits": [
        {
          "counter": "install_server_agent_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Morpheus MCP Server, so you can run agents against it safely.

FAQ

Questions about install_server_agent

What does the install_server_agent tool do? +

Install the Morpheus agent on a server. 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.

How do I enforce a policy on install_server_agent? +

Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for install_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.

What risk level is install_server_agent? +

install_server_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit install_server_agent? +

Yes. Add a rate_limit block to the install_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.

How do I block install_server_agent completely? +

Set action: deny in the PolicyLayer policy for install_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.

What MCP server provides install_server_agent? +

install_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.