list_usage_records

A read tool on the CloudStack MCP server.

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/list-usage-records.md

WHAT IT DOES

What list_usage_records does on CloudStack MCP Server

AI agents call list_usage_records to retrieve information from CloudStack MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_usage_records is rated Low

This tool retrieves and queries usage records without modifying, deleting, or executing any operations. It is a read-only query operation that has no side effects on the infrastructure.

From the tool's definition Tool name 'list_usage_records' and description 'List usage records' indicate a data retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_usage_records 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 list_usage_records, this is the rule to start with:

list_usage_records Allowed

list_usage_records is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_usage_records": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every list_usage_records call is checked against it from then on.

FAQ

Questions about list_usage_records

What does the list_usage_records tool do? +

list_usage_records is a read tool on the CloudStack MCP Server MCP server. It is categorised as a Read tool in the CloudStack MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_usage_records? +

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.

What risk level is list_usage_records? +

list_usage_records is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_usage_records? +

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.

How do I block list_usage_records completely? +

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.

What MCP server provides list_usage_records? +

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

KEEP EXPLORING

More on CloudStack MCP Server, and thousands of servers like it.

This server

All 442 CloudStack MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →