create_datastore
AI agents use create_datastore to create or update resources in Amazon MQ MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon MQ MCP Server environment.
The 'create_datastore' tool creates a new datastore resource, which is a reversible write operation. It modifies the infrastructure state by adding a new resource. While it doesn't delete data (hence not Destructive), it can have significant blast radius if misconfigured—creating wrong datastores could consume resources, incur costs, or disrupt services.
From the tool's definition Tool name is 'create_datastore' which indicates creation of a data storage resource. Context shows this is an Amazon MQ MCP Server for provisioning and managing AMQ brokers, suggesting infrastructure/resource creation.
Attacks that exploit this kind of access
create_datastore. It is categorised as a Write tool in the Amazon MQ MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for create_datastore: 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 Amazon MQ MCP Server. Nothing to install.
create_datastore 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_datastore 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_datastore. 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_datastore is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.