check_glances

Check Glances system monitoring server health via GET /api/3/status. Returns version. Default port 61208.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-glances.md

WHAT IT DOES

What check_glances does on Mcp Nettools

AI agents call check_glances to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_glances is rated Low

This tool reads system monitoring data from a Glances server instance. It is a passive query operation with no side effects. The GET request retrieves diagnostic information only. Blast radius is minimal—misuse would only expose monitoring data visibility, not enable unauthorized actions on monitored systems.

From the tool's definition Tool performs a GET request to retrieve status and version information from a Glances monitoring server. No modification, deletion, or execution of external operations occurs. The description explicitly states it 'Returns version' via a health check endpoint.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_glances safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_glances, this is the rule to start with:

check_glances Allowed

check_glances is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_glances": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_glances call is checked against it from then on.

FAQ

Questions about check_glances

What does the check_glances tool do? +

Check Glances system monitoring server health via GET /api/3/status. Returns version. Default port 61208. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_glances? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_glances: 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 Nettools. Nothing to install.

What risk level is check_glances? +

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

Can I rate-limit check_glances? +

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

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

check_glances is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →