move_user · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_user does on CloudStack MCP Server

AI agents use move_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 move_user needs a policy

Moving a user between accounts modifies user metadata and organizational structure but does not irreversibly delete data (ruling out Destructive) nor execute arbitrary code (ruling out Execute). The operation is reversible—a user can be moved back to the original account. While it affects access control and organization, it remains a data modification action classified as Write.

From the tool's definition Tool name 'move_user' and description 'Move a user to a different account' indicate modification of user account associations. This is a reversible operation that changes data state without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_user Rate-limited

move_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": {
    "move_user": {
      "limits": [
        {
          "counter": "move_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 move_user

What does the move_user tool do? +

Move a user to a different 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 move_user? +

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

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

Can I rate-limit move_user? +

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

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

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