add_user
AI agents use add_user to create or update resources in Windows Operations MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Windows Operations MCP environment.
Based on the tool name 'add_user' on a Windows system administration MCP server, this tool most likely creates a new user account on the Windows system. Creating a user account is a Write operation (reversible via deletion), but carries high severity due to potential privilege escalation or unauthorized access risks. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'add_user' on a Windows system management server; description is empty and uninformative.
Attacks that exploit this kind of access
add_user. It is categorised as a Write tool in the Windows Operations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Windows Operations MCP server in PolicyLayer and add a rule for add_user: 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 Windows Operations MCP. Nothing to install.
add_user 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 add_user 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 add_user. 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.
add_user is provided by the Windows Operations MCP server (sandraschi/windows-operations-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 →