Diff two RouterOS versions — which command paths were added or removed between them. The most common RouterOS support query is
AI agents call routeros_command_diff 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 tool performs a comparative analysis of RouterOS documentation across versions. It reads and searches pre-built documentation data (command reference) to identify version-to-version differences. No commands are executed, no data is modified or deleted, and no external operations are triggered. It is purely informational and aligns with the Read category as it retrieves and queries data without side effects.
From the tool's definition Tool compares and retrieves differences in command paths between two RouterOS versions. The description indicates it is used to query which commands were 'added or removed' — a data retrieval operation that reports information about version changes with no…
Documented attack patterns abuse exactly the kind of access routeros_command_diff 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_diff:
{
"version": "1",
"default": "deny",
"tools": {
"routeros_command_diff": {}
}
}routeros_command_diff 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.
Diff two RouterOS versions — which command paths were added or removed between them. The most common RouterOS support query is. 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_diff: 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_diff 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_diff 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_diff. 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_diff 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.