Browse the RouterOS command tree hierarchy. Given a menu path, returns all direct children (subdirectories, commands, and arguments). Each child includes its type and linked documentation page if available. Useful for discovering what
AI agents call routeros_command_tree to retrieve information from Rosetta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only navigation and discovery tool that retrieves and displays command hierarchy metadata from the documentation index. It neither executes commands, modifies data, nor triggers external operations—it simply queries and presents the structure of available RouterOS commands and their documentation references.
From the tool's definition Tool 'routeros_command_tree' returns a hierarchical view of RouterOS commands and documentation; described as browsing/discovering information with 'returns all direct children' and 'linked documentation page if available' with no modification or execution…
Documented attack patterns abuse exactly the kind of access routeros_command_tree gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rosetta, and nothing reaches the server without passing your rules. This is the rule we recommend for routeros_command_tree:
{
"version": "1",
"default": "deny",
"tools": {
"routeros_command_tree": {}
}
}routeros_command_tree is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Browse the RouterOS command tree hierarchy. Given a menu path, returns all direct children (subdirectories, commands, and arguments). Each child includes its type and linked documentation page if available. Useful for discovering what. It is categorised as a Read tool in the Rosetta MCP Server, which means it retrieves data without modifying state.
Register the Rosetta MCP server in PolicyLayer and add a rule for routeros_command_tree: 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 Rosetta. Nothing to install.
routeros_command_tree 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 routeros_command_tree 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 routeros_command_tree. 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.
routeros_command_tree is provided by the Rosetta MCP server (tikoci/rosetta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rosetta, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Rosetta tools catalogued and risk-classified — across an index of 43,000+ MCP servers.