List Layer 2 bridge configurations.
AI agents call bridges 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 and lists bridge configurations from RouterOS devices. It performs no side effects, creates no new configurations, executes no commands, and does not delete or modify data. It is a pure read operation for network monitoring and inventory purposes, consistent with other read-only tools like 'list_devices', 'system_info', 'logs', and 'neighbors' in the sibling tool set.
From the tool's definition Tool name 'bridges' and description 'List Layer 2 bridge configurations' indicate a query operation that retrieves existing network bridge data without modification or deletion.
Attacks that exploit this kind of access
List Layer 2 bridge configurations. 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 bridges: 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.
bridges 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 bridges 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 bridges. 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.
bridges 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 →