Create a new storage pool
AI agents use create_storage_pool 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.
The tool creates a new storage pool, which is a reversible Write operation. While it allocates infrastructure resources and has blast radius implications (storage pools support VM operations), it does not execute arbitrary code, delete data, or move money. It is Write rather than Execute because pool creation is a configuration action, not code/command execution.
From the tool's definition Tool name 'create_storage_pool' and description 'Create a new storage pool' indicate data/resource creation. This is a Write operation that creates new infrastructure.
Attacks that exploit this kind of access
Create a new storage pool. 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 create_storage_pool: 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.
create_storage_pool 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 create_storage_pool 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 create_storage_pool. 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.
create_storage_pool 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →