assign_server_to_tenant · Morpheus MCP Server MCP

WHAT IT DOES

What assign_server_to_tenant does on Morpheus MCP Server

AI agents use assign_server_to_tenant to create or update resources in Morpheus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Morpheus MCP Server environment.

WHY IT NEEDS A POLICY

Why assign_server_to_tenant needs a policy

This is a Write action because it changes server ownership/assignment across tenants, which is reversible through reassignment. It is not Destructive because the server and its data persist. Severity is high due to the blast radius: misuse could move critical production servers to wrong tenants, causing tenant isolation violations, unauthorized access, or service disruption in a multi-tenant environment.

From the tool's definition Tool description states 'Move a server to a different tenant (sub-account)' — this modifies server-to-tenant associations, a reversible data change in a multi-tenant cloud infrastructure system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_server_to_tenant Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "assign_server_to_tenant": {
      "limits": [
        {
          "counter": "assign_server_to_tenant_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 assign_server_to_tenant

What does the assign_server_to_tenant tool do? +

Move a server to a different tenant (sub-account). It is categorised as a Write tool in the Morpheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on assign_server_to_tenant? +

Register the Morpheus MCP Server MCP server in PolicyLayer and add a rule for assign_server_to_tenant: 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 assign_server_to_tenant? +

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

Can I rate-limit assign_server_to_tenant? +

Yes. Add a rate_limit block to the assign_server_to_tenant 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 assign_server_to_tenant completely? +

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

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