Get database statistics for the RouterOS documentation index. Returns page count, property count, callout count, changelog count, command count, link coverage, version range, documentation export date, and available agent skills. Skills: Community-created agent guides from tikoci/routeros-skills ...
AI agents call routeros_stats 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 purely retrieves and reports aggregate statistics about the documentation index. It reads existing data without side effects, making it a Read category tool. The low severity reflects minimal blast radius—statistics queries cannot harm RouterOS systems or data.
From the tool's definition Tool returns database statistics and metadata: 'page count, property count, callout count, changelog count, command count, link coverage, version range, documentation export date, and available agent skills.' No modification, deletion, or execution of…
Documented attack patterns abuse exactly the kind of access routeros_stats 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_stats:
{
"version": "1",
"default": "deny",
"tools": {
"routeros_stats": {}
}
}routeros_stats 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.
Get database statistics for the RouterOS documentation index. Returns page count, property count, callout count, changelog count, command count, link coverage, version range, documentation export date, and available agent skills. Skills: Community-created agent guides from tikoci/routeros-skills are available as MCP resources at rosetta://skills/{name}. Use the resource listing to browse available skills. Knowledge boundaries: - Documentation: March 2026 Confluence HTML export (317 pages), aligned with long-term ~7.22 - Command tree: RouterOS 7.9–7.23beta2 from inspect.json (with extra-packages from CHR) - No RouterOS v6 data available — v6 syntax and subsystems differ significantly from v7 - For versions older than 7.9, no command tree data exists - Versions older than current long-term are unpatched by MikroTik - Absence of a peripheral in docs doesn. 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_stats: 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_stats 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_stats 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_stats. 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_stats 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.