update_tenant_group · Morpheus MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_tenant_group does on Morpheus MCP Server

AI agents use update_tenant_group 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_group needs a policy

This tool modifies existing tenant group configurations, making it a Write operation. Severity is high because: (1) tenant groups control multi-tenant resource isolation and access control in cloud infrastructure; (2) misconfigured groups could grant unintended access or isolate resources incorrectly; (3) in a multi-tenant environment, mistakes affect multiple users/organizations.

From the tool's definition Tool name 'update_tenant_group' and description 'Update a group within a tenant' indicate modification of tenant configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_tenant_group Rate-limited

update_tenant_group 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_group": {
      "limits": [
        {
          "counter": "update_tenant_group_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_group

What does the update_tenant_group tool do? +

Update a group within a tenant. 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_group? +

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

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

Can I rate-limit update_tenant_group? +

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

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

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