Fetch current RouterOS version numbers from MikroTik
AI agents call routeros_current_versions 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 retrieves publicly available RouterOS version data without creating, modifying, deleting, or executing anything. It is a straightforward query operation with no side effects. Severity is low because misuse would only result in accessing version information, which poses minimal security risk.
From the tool's definition Tool name 'routeros_current_versions' and description 'Fetch current RouterOS version numbers from MikroTik' indicate data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access routeros_current_versions 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_current_versions:
{
"version": "1",
"default": "deny",
"tools": {
"routeros_current_versions": {}
}
}routeros_current_versions 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.
Fetch current RouterOS version numbers from MikroTik. 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_current_versions: 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_current_versions 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_current_versions 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_current_versions. 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_current_versions 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.