generate_usage_records · CloudStack MCP Server MCP

WHAT IT DOES

What generate_usage_records does on CloudStack MCP Server

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

This tool creates usage records that feed billing systems, making it a Write operation. While billing data is critical, the tool itself generates (creates) records rather than moving money directly, so it is not Financial. However, the severity is high because corrupted or fraudulent usage records could lead to incorrect billing, customer disputes, and financial losses.

From the tool's definition Tool name 'generate_usage_records' combined with description 'Generate usage records for billing' indicates creation of billing/usage data records. This is a Write operation that creates new data artifacts.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_usage_records Rate-limited

generate_usage_records 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": {
    "generate_usage_records": {
      "limits": [
        {
          "counter": "generate_usage_records_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 generate_usage_records

What does the generate_usage_records tool do? +

Generate usage records for billing. 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 generate_usage_records? +

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

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

Can I rate-limit generate_usage_records? +

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

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

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