List tags for a resource.
AI agents call list_tags_for_resource 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.
This tool queries and returns existing metadata (tags) associated with a resource. It performs no modification, deletion, execution, or financial transaction. The blast radius of misuse is minimal—an attacker gains only visibility into resource labels, which typically contain non-sensitive organizational information. Classifying as Read with low severity.
From the tool's definition Tool name is 'list_tags_for_resource' and description states 'List tags for a resource.' The verb 'list' and action of retrieving tags are purely informational with no side effects.
Attacks that exploit this kind of access
List tags for a resource. 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 list_tags_for_resource: 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.
list_tags_for_resource 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 list_tags_for_resource 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 list_tags_for_resource. 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.
list_tags_for_resource 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.