Query recent logs with optional service, minimum severity, time window (1-1440 min), text filter, and limit (<=500).
AI agents call query_logs to retrieve information from LogSentry MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters existing log data without creating, modifying, deleting, or executing any operations. It is a classic Read operation with bounded results (limit ≤500). The blast radius is minimal—misuse results in information disclosure of logs that may already be visible to the service account, not unauthorized actions or data destruction.
From the tool's definition Tool description states 'Query recent logs' with filtering parameters (service, severity, time window, text filter, limit). No modification, deletion, or execution capabilities are present. The function is explicitly a query operation with read-only intent.
Attacks that exploit this kind of access
Query recent logs with optional service, minimum severity, time window (1-1440 min), text filter, and limit (<=500). It is categorised as a Read tool in the LogSentry MCP MCP Server, which means it retrieves data without modifying state.
Register the LogSentry MCP server in PolicyLayer and add a rule for query_logs: 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 LogSentry MCP. Nothing to install.
query_logs 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 query_logs 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 query_logs. 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.
query_logs is provided by the LogSentry MCP server (mehtaniravm/logsentrymcpgooglehangout). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →