manage_hyperpod_stacks
AI agents call manage_hyperpod_stacks as a supporting operation in Amazon MQ MCP Server workflows.
With no description available, it is impossible to determine the exact action this tool performs. The name suggests broad management capabilities over HyperPod stacks, which could span Read, Write, Execute, or Destructive categories. Given the ambiguity, 'Other' is assigned with low confidence. Severity is set to medium as management tools typically carry meaningful blast radius risk.
From the tool's definition Tool description is empty and uninformative; tool name 'manage_hyperpod_stacks' suggests management operations on HyperPod stacks
Attacks that exploit this kind of access
manage_hyperpod_stacks. 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 manage_hyperpod_stacks: 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.
manage_hyperpod_stacks 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 manage_hyperpod_stacks 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 manage_hyperpod_stacks. 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.
manage_hyperpod_stacks 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.