manage_hyperpod_stacks
AI agents call manage_hyperpod_stacks as a supporting operation in AWS IoT SiteWise MCP Server workflows.
The description is empty, so there is no direct evidence of what this tool does. The name 'manage_hyperpod_stacks' suggests infrastructure management of HyperPod stacks, which could span Write, Execute, or even Destructive operations. However, without any description, confidence is low. Given the ambiguity and the 'manage' prefix (which could mean create/update/delete), a moderate severity is assigned.
From the tool's definition Tool name: manage_hyperpod_stacks — description is empty and uninformative
Attacks that exploit this kind of access
manage_hyperpod_stacks. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise 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 AWS IoT SiteWise 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 AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.