resize_server · Morpheus MCP Server MCP: Risk & Policy

WHAT IT DOES

What resize_server does on Morpheus MCP Server

AI agents invoke resize_server 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 resize_server needs a policy

Resizing a server typically involves modifying compute resources (CPU, memory, disk) which is an operational action with significant impact. It likely triggers an API call to reconfigure a running or stopped instance. This falls under Execute as it triggers an external infrastructure operation.

From the tool's definition Tool name 'resize_server' on a server that manages cloud infrastructure and provisions resources; description is empty/uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resize_server Rate-limited

resize_server 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": {
    "resize_server": {
      "limits": [
        {
          "counter": "resize_server_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 resize_server

What does the resize_server tool do? +

resize_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 resize_server? +

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

What risk level is resize_server? +

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

Can I rate-limit resize_server? +

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

How do I block resize_server completely? +

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

What MCP server provides resize_server? +

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

// THE FULL RECORD

resize_server is one line of Morpheus MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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