query_system_stats
AI agents call query_system_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.
This tool queries system statistics from a monitoring system without modifying, deleting, or executing operations. The pattern of sibling tools (all list/query operations) and the server's primary purpose (querying statistics and monitoring) confirm this is a data retrieval operation. Tool description is empty, which slightly reduces confidence, but the name and context are clear.
From the tool's definition Tool name 'query_system_stats' indicates querying/retrieving system statistics. Sibling tools on the server are all Read operations ('list_alert_history', 'list_alerts', 'list_containers', 'list_systems', 'query_container_stats'), and the server is described…
Attacks that exploit this kind of access
query_system_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_system_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_system_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_system_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_system_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_system_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 →