AI agents use create_user_with_ssl to create or update resources in Mcp Windows — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Windows environment.
This tool creates new user accounts on Windows systems, which modifies system security posture and access control lists. While reversible (unlike Destructive), it is Write-category because it creates new identity/access objects. Severity is high because compromised creation of privileged user accounts or accounts with excessive permissions could grant unauthorized system access.
From the tool's definition Tool name explicitly states 'create_user' which is a user account creation operation. Description confirms it 'Create a user with SSL requirements.' User creation is a reversible data modification operation (users can be deleted/disabled), and represents…
Documented attack patterns abuse exactly the kind of access create_user_with_ssl gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for create_user_with_ssl:
{
"version": "1",
"default": "deny",
"tools": {
"create_user_with_ssl": {
"limits": [
{
"counter": "create_user_with_ssl_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_user_with_ssl stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a user with SSL requirements. It is categorised as a Write tool in the Mcp Windows MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for create_user_with_ssl: 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 Mcp Windows. Nothing to install.
create_user_with_ssl 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 create_user_with_ssl 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 create_user_with_ssl. 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.
create_user_with_ssl is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.