List all configured RouterOS devices.
AI agents call list_devices 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 or enumerates a static list of configured devices without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an AI agent listing devices cannot harm network infrastructure or data. It may reveal device inventory information, but this is informational only.
From the tool's definition Tool name 'list_devices' indicates a retrieval operation. Description states 'List all configured RouterOS devices' with no mention of modifications, deletions, or state changes. The verb 'list' is characteristic of read-only queries.
Attacks that exploit this kind of access
List all configured RouterOS devices. 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 list_devices: 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.
list_devices 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 list_devices 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 list_devices. 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.
list_devices 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 →