describe_hp_cluster
AI agents call describe_hp_cluster to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'describe_' prefix is a strong signal of a Read operation in AWS APIs, used to fetch metadata and configuration details without modifying state. With no description provided, confidence is moderated but the naming convention is reliable. No destructive, financial, or code execution capability is evident from the name.
From the tool's definition Tool name 'describe_hp_cluster' indicates a query/retrieval operation ('describe' pattern). The empty description prevents full certainty, but 'describe' is a standard AWS read-only operation pattern for retrieving cluster metadata.
Attacks that exploit this kind of access
describe_hp_cluster. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for describe_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.
describe_hp_cluster is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the describe_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 describe_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.
describe_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.