Get comprehensive system information including OS, hardware, and environment.
AI agents call get_system_info to retrieve information from System Monitor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries system information without creating, modifying, deleting, or executing any operations. It is purely informational with no capability to change system state or trigger external actions. The low severity reflects minimal blast radius—an AI agent misusing this tool could only access system metadata, not control systems or delete data.
From the tool's definition Tool name 'get_system_info' and description 'Get comprehensive system information' indicate a query/retrieval operation with no modification or side effects. Returns OS, hardware, and environment data only.
Attacks that exploit this kind of access
Get comprehensive system information including OS, hardware, and environment. It is categorised as a Read tool in the System Monitor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the System Monitor MCP Server 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 System Monitor MCP Server. Nothing to install.
get_system_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_system_info is provided by the System Monitor MCP Server MCP server (praveert/cord). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →