get_metrics
AI agents call get_metrics 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.
'get_metrics' appears to retrieve metrics data without modifying, deleting, or executing external operations. The empty description reduces confidence, but the semantic meaning of 'get' and 'metrics' in the context of AWS IoT SiteWise—a service designed for querying asset and equipment metrics—indicates a read-only query operation with minimal blast radius if misused.
From the tool's definition Tool name 'get_metrics' indicates data retrieval. The description is empty, limiting direct evidence, but the naming convention and placement among other tools like 'aggregate' and 'analyze_*' suggest monitoring/querying operations typical of AWS IoT SiteWise…
Attacks that exploit this kind of access
get_metrics. 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 get_metrics: 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.
get_metrics 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 get_metrics 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 get_metrics. 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.
get_metrics 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.