AI agents use create_user to create or update resources in Redmine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redmine environment.
This tool creates a new user account in the Redmine instance, which is a write operation that adds data to the system. While reversible (users can be deleted), it requires admin privileges and could enable unauthorized account creation if exploited by an AI agent. It is categorized as Write rather than Execute because it performs a direct data creation operation rather than executing arbitrary code or commands.
From the tool's definition Tool name: create_user. Description: 'Create a new user. Requires admin privileges.' The verb 'create' and the action of adding a new user account indicates creation of data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Create a new user. Requires admin privileges. It is categorised as a Write tool in the Redmine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Redmine MCP server in PolicyLayer and add a rule for create_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 Redmine. Nothing to install.
create_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 create_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 create_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.
create_user is provided by the Redmine MCP server (yenpu/redmine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
create_user is one line of Redmine's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →