enable_account · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What enable_account does on CloudStack MCP Server

AI agents use enable_account 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_account needs a policy

Enabling an account modifies account state but does not destroy data or cause irreversible harm. While it could have downstream consequences (account becomes active, users can access resources), the operation itself is reversible and does not delete, overwrite, or transfer financial resources. The Write category is appropriate as it represents a modification of account configuration.

From the tool's definition Tool description states 'Enable a disabled account', which modifies account status (from disabled to enabled). This is a write operation that changes state but is reversible (an account can be disabled again).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

enable_account Rate-limited

enable_account 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_account": {
      "limits": [
        {
          "counter": "enable_account_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_account

What does the enable_account tool do? +

Enable a disabled account. 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_account? +

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

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

Can I rate-limit enable_account? +

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

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

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