get-log-events
AI agents call get-log-events 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 retrieves log events without side effects. The 'get-' prefix and '-events' suffix strongly suggest a query operation that reads existing log data. While the empty description prevents absolute certainty, the naming convention and context within an IoT/monitoring service (SiteWise) indicate this is a standard read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'get-log-events' indicates retrieval of log data with no modification. The empty description limits certainty, but the standard AWS CloudWatch/logging pattern for 'get-log-events' is a read-only operation that fetches historical log entries.
Attacks that exploit this kind of access
get-log-events. 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-log-events: 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-log-events 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-log-events 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-log-events. 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-log-events 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.