get_schedule_details
AI agents call get_schedule_details 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 naming convention 'get_*' strongly suggests this tool queries or retrieves schedule details without modifying data or triggering external operations. The absence of verbs like 'create', 'delete', 'execute', or 'update' in the name indicates a passive read operation. However, confidence is reduced to 0.75 due to the empty description, which prevents verification of actual behavior or potential side effects.
From the tool's definition Tool name 'get_schedule_details' indicates a retrieval operation with the verb 'get', which aligns with Read category semantics (retrieve or query data). Description is empty, limiting direct evidence from documentation.
Attacks that exploit this kind of access
get_schedule_details. 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_schedule_details: 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_schedule_details 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_schedule_details 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_schedule_details. 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_schedule_details 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.