dedicate_pod · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What dedicate_pod does on CloudStack MCP Server

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

This operation modifies infrastructure metadata by assigning a pod to a specific domain or account. It is reversible (a pod can be un-dedicated or re-dedicated), so it is Write rather than Destructive. The blast radius is medium—incorrect dedication could restrict resource access or cause service disruption, but does not permanently delete resources or move money.

From the tool's definition Tool name 'dedicate_pod' and description 'Dedicate a pod to a domain or account' indicate a modification of resource allocation/ownership.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dedicate_pod Rate-limited

dedicate_pod 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": {
    "dedicate_pod": {
      "limits": [
        {
          "counter": "dedicate_pod_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 dedicate_pod

What does the dedicate_pod tool do? +

Dedicate a pod to a domain or 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 dedicate_pod? +

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

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

Can I rate-limit dedicate_pod? +

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

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

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