AI agents use add-user to create or update resources in Dynamic MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dynamic MCP Server environment.
This tool creates a new user entity, which is a reversible write operation. It modifies the user management system by adding a record. Severity is medium because unauthorized user creation could allow attackers to gain accounts and escalate privileges, but the operation is reversible via the sibling 'delete-user' tool. Confidence is high because the name and description directly indicate user creation.
From the tool's definition Tool name 'add-user' and description 'Add a new user' indicate creation of a new user account/record.
Documented attack patterns abuse exactly the kind of access add-user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dynamic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add-user:
{
"version": "1",
"default": "deny",
"tools": {
"add-user": {
"limits": [
{
"counter": "add-user_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add-user 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.
Add a new user. It is categorised as a Write tool in the Dynamic MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dynamic MCP Server 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 Dynamic MCP Server. 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 Dynamic MCP Server MCP server (scitara-cto/dynamic-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dynamic MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Dynamic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.