list_app_schedules
AI agents call list_app_schedules 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.
List operations typically query and return existing data without side effects. The absence of a description prevents full certainty, but the semantic naming convention strongly suggests this tool retrieves schedule information for applications without modifying, executing, or deleting anything. Classified as Read with medium-high confidence due to the empty description.
From the tool's definition Tool name 'list_app_schedules' indicates a listing/enumeration operation with no verb suggesting modification, deletion, or execution. The 'list' prefix is a strong indicator of a read-only data retrieval operation.
Attacks that exploit this kind of access
list_app_schedules. 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_app_schedules: 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_app_schedules 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_app_schedules 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_app_schedules. 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_app_schedules 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.