Return only the total number of Graylog messages that match a query within an absolute timeframe.
AI agents call count_absolute_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 is a read-only operation that retrieves aggregated information (message counts) from Graylog without creating, modifying, deleting, or executing any side effects. It represents passive data retrieval with the lowest blast radius.
From the tool's definition Tool returns only 'total number' of messages matching a query; performs counting/aggregation with no modification of data. The parent server description confirms 'lightweight count-only queries' are supported alongside search capabilities.
Attacks that exploit this kind of access
Return only the total number of Graylog messages that match a query within an absolute timeframe. 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 count_absolute_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.
count_absolute_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 count_absolute_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 count_absolute_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.
count_absolute_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 →