query_container_stats
AI agents call query_container_stats to retrieve information from Beszel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries container statistics without modifying, deleting, or executing operations. It retrieves monitoring data from Beszel's PocketBase backend. Despite the empty description, the naming convention and context of sibling tools strongly indicate this is a read operation with no side effects. Low severity as misuse would only expose system metrics information without operational impact.
From the tool's definition Tool name 'query_container_stats' with sibling tools 'list_alert_history', 'list_alerts', 'list_containers', 'list_systems', and 'query_system_stats' indicate a query-and-retrieve pattern.
Attacks that exploit this kind of access
query_container_stats. It is categorised as a Read tool in the Beszel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Beszel MCP Server MCP server in PolicyLayer and add a rule for query_container_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 Beszel MCP Server. Nothing to install.
query_container_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 query_container_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 query_container_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.
query_container_stats is provided by the Beszel MCP Server MCP server (red5d/beszel-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 →