Get basic system information from the remote host
AI agents call get_system_info to retrieve information from Linux 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 returns system information (hostname, OS version, resource metrics, etc.) without side effects. It is a passive information-gathering operation that does not create, modify, delete, or execute code. While the server enables command execution (Execute/Destructive category), this specific tool is scoped to non-destructive system queries, placing it in the Read category with low severity.
From the tool's definition Tool name 'get_system_info' and description 'Get basic system information from the remote host' indicate a query operation that retrieves data without modifying or executing arbitrary operations. Returns read-only system metadata.
Attacks that exploit this kind of access
Get basic system information from the remote host. It is categorised as a Read tool in the Linux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linux 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 Linux 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 Linux MCP Server MCP server (jnprautomate/linux-mcp-server). 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 →