get_system_info

THE RISK

Low Risk

Why get_system_info needs a policy

This tool retrieves system information without modifying, executing, or destructively altering any state. It is a read-only diagnostic function typical of information gathering utilities.

From the tool's definition Tool name 'get_system_info' and description 'Get system information' indicate a retrieval operation that queries system data with no side effects.

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

POLICY

How to control get_system_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Hugo, 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.

Create a free account and register Hugo — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Hugo tools

Execute build_site Build the Hugo site for production Execute deploy_site Deploy a Hugo site to various platforms Execute start_preview Start Hugo local server for preview Execute stop_preview Stop a running Hugo preview server Execute install_theme Install a Hugo theme Write create_post Create a new Hugo post Write create_site Create a new Hugo site Write update_theme Update an installed Hugo theme

All 15 Hugo tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_system_info

What does the get_system_info tool do? +

Get system information. It is categorised as a Read tool in the Hugo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_system_info? +

Register the Hugo 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 Hugo. 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 Hugo MCP server (sunnycloudyang/hugo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hugo tool call.

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

CHECK YOUR STACK →