Add Amazon S3 as image store backend
AI agents use add_image_store_s3 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.
This tool creates a new S3 backend configuration in CloudStack, modifying the cloud infrastructure's storage layer. While it does not delete data (Destructive) or execute arbitrary code (Execute), it permanently alters infrastructure configuration.
From the tool's definition Tool name 'add_image_store_s3' and description 'Add Amazon S3 as image store backend' indicate creation/modification of infrastructure configuration. The verb 'add' combined with 'image_store' shows this creates or registers a new storage backend resource.
Attacks that exploit this kind of access
Add Amazon S3 as image store backend. 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 add_image_store_s3: 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.
add_image_store_s3 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 add_image_store_s3 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 add_image_store_s3. 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.
add_image_store_s3 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 →