Search Graylog messages within a relative timeframe (seconds) counted back from now.
AI agents call search_relative_logs to retrieve information from Graylog MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is purely informational: it queries and retrieves log data from Graylog without creating, modifying, deleting, or executing any operations. The description explicitly indicates it searches messages (retrieves data) using relative timeframes. Misuse by an AI agent would be limited to unauthorized information disclosure, which has low blast radius compared to tools that modify or delete data.
From the tool's definition Tool performs 'Search Graylog messages' - a query operation that retrieves log data with 'no side effects' as it only reads existing log entries within specified time windows.
Attacks that exploit this kind of access
Search Graylog messages within a relative timeframe (seconds) counted back from now. It is categorised as a Read tool in the Graylog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Graylog MCP Server MCP server in PolicyLayer and add a rule for search_relative_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 Graylog MCP Server. Nothing to install.
search_relative_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 search_relative_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 search_relative_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.
search_relative_logs is provided by the Graylog MCP Server MCP server (princegupta1999/graylog-mcp). 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 →