update_resource_count
Recalculate and update resource usage counts
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/update-resource-count.md
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 update_resource_count is rated Medium
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
The rule that runs update_resource_count safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_resource_count, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every update_resource_count call is checked against it from then on.
Questions about update_resource_count
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.
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.
update_resource_count is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on CloudStack MCP Server, and thousands of servers like it.
This server
Across the catalogue