Get system information and resource usage.
AI agents call system_info to retrieve information from RouterOS 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 system metrics and status information from RouterOS devices. It performs no modifications, does not execute commands with side effects, and does not delete or move data. The operation is purely informational, making it a Read category tool with low severity—misuse by an AI agent would only expose internal system details without enabling harmful actions on the network infrastructure.
From the tool's definition Tool name 'system_info' and description 'Get system information and resource usage' indicate a query-only operation that retrieves data without modification or side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get system information and resource usage. It is categorised as a Read tool in the RouterOS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RouterOS MCP Server MCP server in PolicyLayer and add a rule for 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 RouterOS MCP Server. Nothing to install.
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 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 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.
system_info is provided by the RouterOS MCP Server MCP server (sevaepsteyn/routeros_mcp). 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 →