describe_log_groups
AI agents call describe_log_groups 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.
AWS describe_* operations are standardized read-only queries that return information about resources. The tool retrieves or lists log group configurations and metadata with no side effects. While the description is empty, the naming pattern is strong evidence this is a Read operation with low severity impact, as it only fetches data.
From the tool's definition Tool name 'describe_log_groups' follows AWS API naming convention for retrieve/query operations (describe_* actions are read-only in AWS APIs). The describe prefix indicates fetching metadata or configuration about log groups without modification.
Attacks that exploit this kind of access
describe_log_groups. 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 describe_log_groups: 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.
describe_log_groups 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 describe_log_groups 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 describe_log_groups. 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.
describe_log_groups 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.