Low Risk

get_system_status

Get system health and storage information

How to control get_system_status ↓

What get_system_status does on MCParr Server

AI agents call get_system_status to retrieve information from MCParr Server 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_status needs a policy

This tool retrieves system health metrics and storage information without modifying any data, executing commands, or triggering side effects. It is a pure read operation that falls into the Read category with low severity, as misuse would only expose informational data about the system rather than enable destructive, financial, or executable actions.

From the tool's definition Tool name 'get_system_status' and description 'Get system health and storage information' indicate data retrieval with no modification or execution. Returns status/monitoring data only.

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

How to control get_system_status

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

  1. Create a free account and register MCParr Server — 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_status

What does the get_system_status tool do? +

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

How do I enforce a policy on get_system_status? +

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

Enforce policy on every MCParr Server tool call.

Start from MCParr Server, 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.

4 MCParr Server 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.