enable_user · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What enable_user does on CloudStack MCP Server

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

WHY IT NEEDS A POLICY

Why enable_user needs a policy

The tool modifies user account state (disabled → enabled) but this change is reversible—the user can be disabled again. It affects access control rather than creating/deleting data irreversibly. Severity is medium because enabling a user grants access privileges, which could have downstream security implications depending on that user's permissions, but the action itself is non-destructive and can be undone.

From the tool's definition Tool name 'enable_user' and description 'Enable a previously disabled user' indicates modification of user account status, a reversible state change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enable_user Rate-limited

enable_user 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": {
    "enable_user": {
      "limits": [
        {
          "counter": "enable_user_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 CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about enable_user

What does the enable_user tool do? +

Enable a previously disabled user. It is categorised as a Write tool in the CloudStack 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 enable_user? +

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

What risk level is enable_user? +

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

Can I rate-limit enable_user? +

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

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

enable_user is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.