Get full configuration export.
AI agents call config to retrieve information from RouterOS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves sensitive configuration data from RouterOS devices (firewall rules, NAT settings, user accounts, VPN configurations, etc.) without modifying it. While it is read-only, the severity is high because the exported configuration could contain credentials, network topology details, and security policies that could be leveraged for reconnaissance or lateral movement if exposed to an untrusted actor.
From the tool's definition Tool name 'config' with description 'Get full configuration export' indicates data retrieval without modification. The word 'Get' confirms a read operation, and 'full configuration export' describes querying the complete device configuration state.
Attacks that exploit this kind of access
Get full configuration export. It is categorised as a Read tool in the RouterOS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RouterOS MCP Server MCP server in PolicyLayer and add a rule for config: 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 RouterOS MCP Server. Nothing to install.
config 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 config 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 config. 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.
config is provided by the RouterOS MCP Server MCP server (sevaepsteyn/routeros_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →