mikrotik_get_logs_by_topic

What mikrotik_get_logs_by_topic does on MikroTik Cursor MCP

AI agents call mikrotik_get_logs_by_topic to retrieve information from MikroTik Cursor MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why mikrotik_get_logs_by_topic is rated Low

This tool only retrieves historical log data from a MikroTik router. It performs a passive read operation with no side effects, no data modifications, and no irreversible actions. The blast radius of misuse is minimal—an attacker could view router logs to gather intelligence but cannot alter system state or cause damage through this tool alone.

From the tool's definition Tool retrieves logs for a specific topic/facility without modifying or deleting any data. The name 'get_logs_by_topic' and description 'Gets logs' explicitly indicate a read operation.

The rule that runs mikrotik_get_logs_by_topic safely

PolicyLayer is an MCP gateway: it sits between your AI agents and MikroTik Cursor MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mikrotik_get_logs_by_topic, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mikrotik_get_logs_by_topic": {}
  }
}

Questions about mikrotik_get_logs_by_topic