Low Risk

get_system_info

Get system information (OS, CPU, memory, disks) for a server.

How to control get_system_info ↓

What get_system_info does on Komodo

AI agents call get_system_info 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_system_info needs a policy

This tool performs a read-only query of system metadata. It retrieves data about server hardware and OS configuration without any side effects, state changes, or capability to execute commands or modify resources. Blast radius is minimal—an AI agent misusing this tool could only learn server specs, not cause damage or unauthorized operations.

From the tool's definition Tool name is 'get_system_info' and description states it retrieves system information (OS, CPU, memory, disks) with no modification or execution capability mentioned.

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

How to control get_system_info

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_system_info:

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

get_system_info 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_system_info

What does the get_system_info tool do? +

Get system information (OS, CPU, memory, disks) 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_system_info? +

Register the Komodo MCP server in PolicyLayer and add a rule for get_system_info: 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_system_info? +

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

Can I rate-limit get_system_info? +

Yes. Add a rate_limit block to the get_system_info 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_system_info completely? +

Set action: deny in the PolicyLayer policy for get_system_info. 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_system_info? +

get_system_info 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.