update_hp_cluster
AI agents use update_hp_cluster to create or update resources in AWS IoT SiteWise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS IoT SiteWise MCP Server environment.
The verb 'update' signals a reversible write operation that modifies cluster state. Given the AWS IoT SiteWise context (industrial IoT data processing) and 'hp_cluster' reference (likely high-performance compute infrastructure), this tool can alter cluster settings, scaling, or configuration—affecting data pipeline operations and resource allocation.
From the tool's definition Tool name 'update_hp_cluster' indicates modification of a high-performance cluster configuration. Description is empty, limiting direct textual evidence.
Attacks that exploit this kind of access
update_hp_cluster. It is categorised as a Write tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for update_hp_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 AWS IoT SiteWise MCP Server. Nothing to install.
update_hp_cluster 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 update_hp_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 update_hp_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.
update_hp_cluster 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.