Connect to a new RabbitMQ broker using OAuth. It only applies to RabbitMQ broker which authentication strategy is config_managed. broker_hostname: The hostname of the broker. For example, b-a9565a64-da39-4afc-9239-c43a9376b5ba.mq.us-east-1.on.aws, b-9560b8e1-3d33-4d91-9488-a3dc4a61dfe7.mq.us-eas...
Part of the Amazon MQ MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke rabbimq_broker_initialize_connection_with_oauth to trigger processes or run actions in Amazon MQ MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
rabbimq_broker_initialize_connection_with_oauth can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
rabbimq_broker_initialize_connection_with_oauth:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Amazon MQ MCP Server policy for all 23 tools.
Agents calling execute-class tools like rabbimq_broker_initialize_connection_with_oauth have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
rabbimq_broker_initialize_connection_with_oauth is one of the high-risk operations in Amazon MQ MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Connect to a new RabbitMQ broker using OAuth. It only applies to RabbitMQ broker which authentication strategy is config_managed. broker_hostname: The hostname of the broker. For example, b-a9565a64-da39-4afc-9239-c43a9376b5ba.mq.us-east-1.on.aws, b-9560b8e1-3d33-4d91-9488-a3dc4a61dfe7.mq.us-east-1.amazonaws.com oauth_token: A valid access token. It is categorised as a Execute tool in the Amazon MQ MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for rabbimq_broker_initialize_connection_with_oauth. 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.
rabbimq_broker_initialize_connection_with_oauth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rabbimq_broker_initialize_connection_with_oauth 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 rabbimq_broker_initialize_connection_with_oauth. 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.
rabbimq_broker_initialize_connection_with_oauth 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.