list_resource_details

List resource details for virtual machine

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-resource-details.md

WHAT IT DOES

What list_resource_details does on CloudStack MCP Server

AI agents call list_resource_details 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_resource_details is rated Low

This tool retrieves and displays information about virtual machine resources. The verb 'list' and the absence of any language indicating modification, deletion, or external command execution clearly places this in the Read category. The blast radius is minimal as it only exposes existing information about infrastructure state without side effects.

From the tool's definition Tool name 'list_resource_details' and description 'List resource details for virtual machine' indicate a query/retrieval operation with no modification or deletion capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_resource_details Allowed

list_resource_details 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_resource_details": {}
  }
}

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_resource_details call is checked against it from then on.

FAQ

Questions about list_resource_details

What does the list_resource_details tool do? +

List resource details for virtual machine. 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_resource_details? +

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

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

Can I rate-limit list_resource_details? +

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

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

list_resource_details 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 →