Clears all logs from MikroTik device
AI agents call mikrotik_clear_logs to permanently remove resources in MikroTik Cursor MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes audit/diagnostic logs without the ability to recover them. Log deletion is a destructive operation that cannot be undone and eliminates evidence trails, making it a high-severity destructive action. An AI agent misusing this could eliminate critical security and operational audit records from network infrastructure.
From the tool's definition Tool name 'mikrotik_clear_logs' combined with description 'Clears all logs from MikroTik device' explicitly indicates irreversible deletion of log data.
Attacks that exploit this kind of access
Clears all logs from MikroTik device. It is categorised as a Destructive tool in the MikroTik Cursor MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_clear_logs: 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 MikroTik Cursor MCP. Nothing to install.
mikrotik_clear_logs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the mikrotik_clear_logs 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 mikrotik_clear_logs. 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.
mikrotik_clear_logs is provided by the MikroTik Cursor MCP server (kevinpez/mikrotik-cursor-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 →