get_system_status

THE RISK

Low Risk

Why get_system_status needs a policy

Despite the server's overall purpose (penetration testing with Execute/Destructive capabilities), this specific tool is a simple monitoring/query function that reads system state (CPU, memory, disk, process info). It retrieves data only and cannot alter system state or trigger external operations. Classification as Read is appropriate even in a sensitive pentesting context, as the tool itself is informational-only.

From the tool's definition Tool name 'get_system_status' and description 'Get your OS system resource usage and status' indicate retrieval of system metrics without modification. No side effects, no code execution, no destructive operations.

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

POLICY

How to control get_system_status

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

policy.json

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

get_system_status 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 Pentest MCP Server — 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 Pentest MCP Server tools

Destructive kill_session Terminate a tmux session Execute execute Execute a command in a persistent tmux session with trigger-based monitoring Execute recover_sessions Find and reconnect to orphaned tmux sessions Execute create_session Create a new persistent tmux session Execute send_input Send input to an interactive session Write upload_file Upload a file to the your OS system Read parse_tool_output Parse common pentest tool outputs (nmap XML, JSON, etc.) Read download_file Download a file from the your OS system

All 12 Pentest MCP Server 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_status

What does the get_system_status tool do? +

Get your OS system resource usage and status. It is categorised as a Read tool in the Pentest MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_system_status? +

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

What risk level is get_system_status? +

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

Can I rate-limit get_system_status? +

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

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

get_system_status is provided by the Pentest MCP Server MCP server (layesec006/pentest-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pentest MCP Server tool call.

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

CHECK YOUR STACK →