Low Risk

get_system_info

Get WSL system information

How to control get_system_info ↓

What get_system_info does on Mcp Wsl Exec

AI agents call get_system_info to retrieve information from Mcp Wsl Exec 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 retrieves and returns system information about the WSL environment (such as OS version, hardware details, or configuration). It performs no side effects, makes no modifications, and executes no external operations. It is purely informational and read-only, making it a Read category tool with low severity.

From the tool's definition The tool name 'get_system_info' and description 'Get WSL system information' indicate a query operation that retrieves system metadata without modifying or executing anything.

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 Mcp Wsl Exec, 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 Mcp Wsl Exec — 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 WSL system information. It is categorised as a Read tool in the Mcp Wsl Exec MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_system_info? +

Register the Mcp Wsl Exec 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 Mcp Wsl Exec. 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 Mcp Wsl Exec MCP server (spences10/mcp-wsl-exec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Wsl Exec tool call.

Start from Mcp Wsl Exec, 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.

7 Mcp Wsl Exec 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.