Updates an existing user group on MikroTik device
AI agents use mikrotik_update_user_group to create or update resources in MikroTik MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MikroTik MCP environment.
This tool modifies (rather than deletes) user group configurations, which are reversible changes. However, user groups control access permissions and authentication across a network device, so unauthorized or incorrect modifications could grant/restrict access to critical network functions, creating a high-severity impact.
From the tool's definition Tool name and description indicate 'Updates an existing user group' — a modification operation on MikroTik RouterOS.
Attacks that exploit this kind of access
Updates an existing user group on MikroTik device. It is categorised as a Write tool in the MikroTik MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MikroTik MCP server in PolicyLayer and add a rule for mikrotik_update_user_group: 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_update_user_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mikrotik_update_user_group 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_update_user_group. 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_update_user_group 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 →