update_group · Redmine MCP: Risk & Policy | PolicyLayer

WHAT IT DOES

What update_group does on Redmine

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_group needs a policy

Renaming a group is a reversible write operation that modifies metadata. It does not delete data (thus not Destructive), does not execute arbitrary code (thus not Execute), and does not involve financial transactions. The severity is medium because renaming groups could affect many users' access if the group name is used for identification or reference, but the change can be undone by renaming again.

From the tool's definition Tool description states 'Rename a group', which modifies an existing group's name attribute. This is a reversible change to group data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_group Rate-limited

update_group 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_group": {
      "limits": [
        {
          "counter": "update_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Redmine, so you can run agents against it safely.

FAQ

Questions about update_group

What does the update_group tool do? +

Rename a group. 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.

How do I enforce a policy on update_group? +

Register the Redmine MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_group? +

update_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_group? +

Yes. Add a rate_limit block to the update_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.

How do I block update_group completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_group? +

update_group is provided by the Redmine MCP server (KalvadTech/redmine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.