update_tenant · Morpheus MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_tenant does on Morpheus MCP Server

AI agents use update_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 update_tenant needs a policy

The tool modifies tenant configuration in a multi-tenant cloud infrastructure management system (Morpheus). While reversible (not Destructive), this is a Write operation with high blast radius because: (1) it modifies administrative entities in a shared infrastructure platform, (2) unintended tenant updates could affect access controls, billing, resource quotas, or isolation boundaries across multiple…

From the tool's definition Tool name is 'update_tenant' and description states 'Update an existing tenant. Only fields you provide are changed.' This directly indicates modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_tenant Rate-limited

update_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": {
    "update_tenant": {
      "limits": [
        {
          "counter": "update_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 update_tenant

What does the update_tenant tool do? +

Update an existing tenant. Only fields you provide are changed. 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 update_tenant? +

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

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

Can I rate-limit update_tenant? +

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

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

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