list_applications
AI agents call list_applications 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 tool performs data retrieval by listing applications, which is a non-destructive query operation with no side effects. In AWS IoT SiteWise context, listing applications would retrieve configuration or metadata about deployed applications. This poses minimal risk when misused—an agent could at worst enumerate and read application metadata, not modify, delete, or execute operations.
From the tool's definition Tool name 'list_applications' indicates a query/enumeration operation. The pattern matches standard Read operations (list, get, fetch) that retrieve data without side effects. Empty description reduces confidence slightly, but the name is unambiguous.
Attacks that exploit this kind of access
list_applications. 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_applications: 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_applications 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_applications 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_applications. 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_applications 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.