Check which RouterOS versions include a specific command path. Returns the list of versions where the command exists, plus first_seen/last_seen. If the command exists in our earliest tracked version, a note warns that it likely predates our data — check the documentation page for earlier version ...
AI agents call routeros_command_version_check 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 queries documentation metadata to retrieve version compatibility information about RouterOS commands. It performs read-only lookups against the MikroTik documentation database without side effects, matching the 'Read' category definition of retrieving or querying data with no side effects.
From the tool's definition Tool description states it "Check[s] which RouterOS versions include a specific command path" and "Returns the list of versions where the command exists" — pure information retrieval with no modification, deletion, or execution of commands.
Documented attack patterns abuse exactly the kind of access routeros_command_version_check 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_version_check:
{
"version": "1",
"default": "deny",
"tools": {
"routeros_command_version_check": {}
}
}routeros_command_version_check 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.
Check which RouterOS versions include a specific command path. Returns the list of versions where the command exists, plus first_seen/last_seen. If the command exists in our earliest tracked version, a note warns that it likely predates our data — check the documentation page for earlier version references. Useful for answering. 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_version_check: 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_version_check 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_version_check 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_version_check. 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_version_check 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.