update_resource_count · CloudStack MCP Server MCP

WHAT IT DOES

What update_resource_count does on CloudStack MCP Server

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

This tool modifies resource usage counts in a CloudStack infrastructure system. While not destructive (data can be recalculated), it writes/modifies state that affects billing, quotas, and resource allocation decisions. The high severity reflects potential for disruption if counts are incorrectly updated—affecting VM provisioning limits, quota enforcement, and billing accuracy.

From the tool's definition Tool name 'update_resource_count' and description 'Recalculate and update resource usage counts' indicate modification of resource tracking data. The verb 'update' is explicitly used, confirming data alteration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_resource_count Rate-limited

update_resource_count 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_resource_count": {
      "limits": [
        {
          "counter": "update_resource_count_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 update_resource_count

What does the update_resource_count tool do? +

Recalculate and update resource usage counts. 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 update_resource_count? +

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

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

Can I rate-limit update_resource_count? +

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

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

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