Look up MikroTik hardware specs, performance benchmarks, or search for devices matching criteria. 144 products from mikrotik.com (March 2026). Returns hardware specs, official test results, block diagram URLs, and pricing. How it works: - If query matches a product name or code exactly → returns ...
AI agents call routeros_device_lookup 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 informational lookups and searches against documentation and product specifications. It has no side effects, cannot modify or delete data, does not execute commands, and does not involve financial transactions. The query-based search and filter operations are purely retrievals from a SQLite FTS5 index of static product data.
From the tool's definition Tool retrieves hardware specs, performance benchmarks, pricing, and test results from a static database of 144 MikroTik products.
Documented attack patterns abuse exactly the kind of access routeros_device_lookup 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_device_lookup:
{
"version": "1",
"default": "deny",
"tools": {
"routeros_device_lookup": {}
}
}routeros_device_lookup 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.
Look up MikroTik hardware specs, performance benchmarks, or search for devices matching criteria. 144 products from mikrotik.com (March 2026). Returns hardware specs, official test results, block diagram URLs, and pricing. How it works: - If query matches a product name or code exactly → returns full specs + test results + block diagram - Otherwise → FTS search + optional structured filters → returns matching devices (compact) - Filters can be used alone (no query) to find devices by capability Test results (from mikrotik.com per-product pages): - Ethernet: bridging/routing throughput at 64/512/1518 byte packets (kpps + Mbps) - IPSec: tunnel throughput with various AES/SHA configurations - Key metric:. 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_device_lookup: 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_device_lookup 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_device_lookup 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_device_lookup. 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_device_lookup 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.