Gets logs filtered by severity level
AI agents call mikrotik_get_logs_by_severity to retrieve information from MikroTik MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing log data with a filter applied. It does not create, modify, delete, execute commands, or move money. The read operation on logs poses minimal risk—at worst an agent could learn about network events, but cannot alter system state or configurations. Severity is low because log access is informational only.
From the tool's definition Tool name 'mikrotik_get_logs_by_severity' and description 'Gets logs filtered by severity level' indicate a query/retrieval operation. The verb 'Gets' and the filtering operation are characteristic of read-only data access with no side effects.
Attacks that exploit this kind of access
Gets logs filtered by severity level. It is categorised as a Read tool in the MikroTik MCP MCP Server, which means it retrieves data without modifying state.
Register the MikroTik MCP server in PolicyLayer and add a rule for mikrotik_get_logs_by_severity: 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 MCP. Nothing to install.
mikrotik_get_logs_by_severity 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 mikrotik_get_logs_by_severity 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_get_logs_by_severity. 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_get_logs_by_severity is provided by the MikroTik MCP server (tarcisiodier/mcp-mikrotik). 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 →