stats
Returns a snapshot of container resource usage (CPU, memory, network/block I/O, PIDs) as structured data.
This record as markdown: /tools/io-github-dave-london-go/stats.md
What stats does on Go
AI agents call stats to retrieve information from Go without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stats is rated Low
The tool retrieves and reports real-time statistics about container resource consumption. It performs a read-only query of container metrics and returns structured diagnostic information without triggering any state changes, side effects, or resource modifications. The action is non-destructive and informational in nature.
From the tool's definition Returns a snapshot of container resource usage (CPU, memory, network/block I/O, PIDs) as structured data - this is purely observational with no mention of modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs stats safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stats, this is the rule to start with:
stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Go, apply this rule, and every stats call is checked against it from then on.
Questions about stats
Returns a snapshot of container resource usage (CPU, memory, network/block I/O, PIDs) as structured data. It is categorised as a Read tool in the Go MCP Server, which means it retrieves data without modifying state.
Register the Go MCP server in PolicyLayer and add a rule for 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 Go. Nothing to install.
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 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 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.
stats is provided by the Go MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Go, and thousands of servers like it.
This server
Across the catalogue