Gets currently active/logged-in users
AI agents call mikrotik_get_active_users to retrieve information from MikroTik Cursor MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only information about active user sessions on a MikroTik router. It has no side effects, does not execute commands, and does not modify any state. The blast radius of misuse is low — an attacker could learn who is logged in, but cannot take unauthorized actions beyond information disclosure. Therefore, it is classified as Read with low severity.
From the tool's definition Tool name contains 'get' and description states 'Gets currently active/logged-in users' — a query operation that retrieves session state information without modifying or executing anything.
Attacks that exploit this kind of access
Gets currently active/logged-in users. It is categorised as a Read tool in the MikroTik Cursor MCP MCP Server, which means it retrieves data without modifying state.
Register the MikroTik Cursor MCP server in PolicyLayer and add a rule for mikrotik_get_active_users: 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_get_active_users 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_active_users 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_active_users. 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_active_users 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 →