get_log_stats
AI agents call get_log_stats to retrieve information from Mezmo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_log_stats' and the server's stated purpose of retrieving and analyzing logs strongly suggest this retrieves statistical information about logs without modifying them. The empty description reduces confidence slightly, but the context (log retrieval server, sibling read-only tools) indicates this is a read operation with no side effects.
From the tool's definition Tool named 'get_log_stats' with empty description; sibling tools 'get_logs' and 'list_apps' are query/retrieval operations. Server explicitly focused on 'retrieving and filtering logs' with 'quota-conscious design' indicating read-only log analysis.
Attacks that exploit this kind of access
get_log_stats. It is categorised as a Read tool in the Mezmo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mezmo MCP Server MCP server in PolicyLayer and add a rule for get_log_stats: 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 Mezmo MCP Server. Nothing to install.
get_log_stats 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 get_log_stats 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 get_log_stats. 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.
get_log_stats is provided by the Mezmo MCP Server MCP server (riefer02/mezmo-logs-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 →