connect-jump-host-cache-cluster
AI agents call connect-jump-host-cache-cluster as a supporting operation in Amazon MQ MCP Server workflows.
The description is empty, providing no information about what this tool actually does. The name suggests establishing a connection to a jump host and cache cluster, which could be Read (querying connection info), Execute (establishing a network connection/tunnel), or Write (configuring connection settings). Without more information, I cannot determine the exact category.
From the tool's definition Tool name: connect-jump-host-cache-cluster; description is empty
Attacks that exploit this kind of access
connect-jump-host-cache-cluster. It is categorised as a Other tool in the Amazon MQ MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for connect-jump-host-cache-cluster: 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.
connect-jump-host-cache-cluster is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the connect-jump-host-cache-cluster 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 connect-jump-host-cache-cluster. 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.
connect-jump-host-cache-cluster 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.