AI agents call list_usage_records to retrieve information from CloudStack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves billing and usage information, which is a Read operation (no side effects). However, it accesses sensitive financial/billing data that could be abused to extract cost information, pricing details, or customer usage patterns. Severity is medium (not high) because viewing existing records carries lower risk than executing financial transactions or modifying data.
From the tool's definition Tool name 'list_usage_records' and description 'List usage records for billing' indicate the tool retrieves/queries historical billing data without modifying it.
Documented attack patterns abuse exactly the kind of access list_usage_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CloudStack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_usage_records:
{
"version": "1",
"default": "deny",
"tools": {
"list_usage_records": {}
}
}list_usage_records is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List usage records for billing. It is categorised as a Read tool in the CloudStack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for list_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.
list_usage_records is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_usage_records is provided by the CloudStack MCP Server MCP server (phantosmax/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CloudStack MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
45 CloudStack MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.