Low Risk

get_server_stats

Get system stats (CPU, memory, disk) for a server.

How to control get_server_stats ↓

What get_server_stats does on Komodo

AI agents call get_server_stats to retrieve information from Komodo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_server_stats needs a policy

This tool queries and retrieves server performance metrics (CPU, memory, disk usage). It performs no modifications, deletions, code execution, or financial operations. The blast radius of misuse is minimal—an agent could only retrieve system statistics, which provides no ability to alter infrastructure or cause harm beyond information disclosure. This is a straightforward Read operation.

From the tool's definition Tool name 'get_server_stats' and description 'Get system stats (CPU, memory, disk) for a server' indicate a retrieval operation with no data modification or side effects.

Documented attack patterns abuse exactly the kind of access get_server_stats gives an agent:

How to control get_server_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and Komodo, and nothing reaches the server without passing your rules. This is the rule we recommend for get_server_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_server_stats": {}
  }
}

get_server_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Komodo — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_server_stats

What does the get_server_stats tool do? +

Get system stats (CPU, memory, disk) for a server. It is categorised as a Read tool in the Komodo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_server_stats? +

Register the Komodo MCP server in PolicyLayer and add a rule for get_server_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 Komodo. Nothing to install.

What risk level is get_server_stats? +

get_server_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_server_stats? +

Yes. Add a rate_limit block to the get_server_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.

How do I block get_server_stats completely? +

Set action: deny in the PolicyLayer policy for get_server_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.

What MCP server provides get_server_stats? +

get_server_stats is provided by the Komodo MCP server (myrikld/komodo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Komodo tool call.

Start from Komodo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

53 Komodo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.