AI agents use create_group 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 group resource in Redmine, which is a reversible Write operation (groups can be deleted). However, the severity is 'high' rather than 'medium' because: (1) it requires admin privileges, indicating systemic importance; (2) creating groups can be chained with 'add_user_to_group' and 'add_membership' to establish unauthorized access patterns; (3) an AI agent with admin credentials could create…
From the tool's definition Tool name 'create_group' and description 'Create a new group' indicate irreversible creation of a new security/organizational entity. 'Requires admin privileges' confirms this is a sensitive administrative operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Create a new group. 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_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 Redmine. Nothing to install.
create_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 create_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 create_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.
create_group 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.
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 →