Create a ActiveMQ or RabbitMQ broker on AmazonMQ. Args: region: AWS region code (e.g., 'us-east-1', 'eu-west-1'). broker_name: The name given to the broker. engine_type: The engine type of the broker. Possible values: "RABBITMQ" and "ACTIVEMQ". deployment_mode: The broker deploym...
Handles credentials or secrets (password); High parameter count (10 properties)
Part of the Amazon MQ MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use create_broker to create or modify resources in Amazon MQ MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_broker repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Amazon MQ MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
create_broker:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Amazon MQ MCP Server policy for all 23 tools.
Agents calling write-class tools like create_broker have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Create a ActiveMQ or RabbitMQ broker on AmazonMQ. Args: region: AWS region code (e.g., 'us-east-1', 'eu-west-1'). broker_name: The name given to the broker. engine_type: The engine type of the broker. Possible values: "RABBITMQ" and "ACTIVEMQ". deployment_mode: The broker deployment mode. Possible values for ACTIVEMQ engine type: SINGLE_INSTANCE, ACTIVE_STANDBY_MULTI_AZ and possible values for RABBITMQ engine type: SINGLE_INSTANCE, CLUSTER_MULTI_AZ. username: The username to access the broker. password: The password for the user. engine_version: The broker engine version. Defaults to the latest available version for the specified broker engine type. It should also be unspecified to use the latest version. publicly_accessible: Enables connections from applications outside of the VPC that hosts the broker's subnets. Default to True for publicly accessible broker. host_instance_type: The broker instance type. Default to production-ready instance type "mq.m5.xlarge". auto_minor_version_upgrade: Whether or not to enable minor version automatic upgrade. Default is true. Returns: Response from API. 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.
Add a rule in your Intercept YAML policy under the tools section for create_broker. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Amazon MQ MCP Server MCP server.
create_broker 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_broker rule in your Intercept 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 Intercept policy for create_broker. 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_broker is provided by the Amazon MQ MCP Server MCP server (awslabs.amazon-mq-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.