New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

system_get_status

Get comprehensive system status including CPU, memory, disk, network, and load.

SERVERAapanel SOURCEnipunanirmal/aapanel-mcp
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/aapanel-mcp/system-get-status.md

What system_get_status does on Aapanel

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

Why system_get_status is rated Low

This tool retrieves system metrics and status information without creating, modifying, deleting, executing code, or moving money. It is purely informational with no ability to affect system state. The context of sibling monitoring tools (abnormal_check_*) further confirms this is part of a monitoring/observability function rather than an operational tool.

From the tool's definition Tool name 'system_get_status' and description 'Get comprehensive system status including CPU, memory, disk, network, and load' indicate a retrieval/query operation with no side effects.

Risk signalsAdmin/system-level operation

Questions about system_get_status

What does the system_get_status tool do? +

Get comprehensive system status including CPU, memory, disk, network, and load. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on system_get_status? +

Register the Aapanel MCP server in PolicyLayer and add a rule for system_get_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 Aapanel. Nothing to install.

What risk level is system_get_status? +

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

Can I rate-limit system_get_status? +

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

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

system_get_status is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Aapanel, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Aapanel's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.