Count log entries by severity level (ERROR, WARN, INFO, DEBUG)
AI agents call count_by_level to retrieve information from Log Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing log data to provide counts grouped by severity level. It has no side effects, does not modify logs, does not execute commands, and does not create or delete data. It is purely a read operation that queries log information, making it a Read category tool.
From the tool's definition Tool counts log entries by severity level (ERROR, WARN, INFO, DEBUG) - performs aggregation and retrieval of log data without modification, deletion, or execution.
Attacks that exploit this kind of access
Count log entries by severity level (ERROR, WARN, INFO, DEBUG). It is categorised as a Read tool in the Log Analyzer MCP Server, which means it retrieves data without modifying state.
Register the Log Analyzer MCP server in PolicyLayer and add a rule for count_by_level: 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 Log Analyzer. Nothing to install.
count_by_level 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_by_level 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_by_level. 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_by_level is provided by the Log Analyzer MCP server (yufeizhou666/my_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 →