update_user · Redmine MCP OAuth Server MCP: Risk & Policy

WHAT IT DOES

What update_user does on Redmine MCP OAuth Server

AI agents use update_user to create or update resources in Redmine MCP OAuth Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Redmine MCP OAuth Server environment.

WHY IT NEEDS A POLICY

Why update_user needs a policy

The tool creates or modifies user records in Redmine without deleting data or moving money. It is classified as Write rather than Execute because it performs a direct data update operation. Severity is medium because misuse could modify user credentials, permissions, or account details affecting multiple users, but the operation is reversible and does not cause irreversible damage or financial impact.

From the tool's definition Tool name 'update_user' and description 'Update a Redmine user' explicitly indicate modification of user data via a dict of fields to change. This is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_user Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_user": {
      "limits": [
        {
          "counter": "update_user_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 MCP OAuth Server, so you can run agents against it safely.

FAQ

Questions about update_user

What does the update_user tool do? +

Update a Redmine user. updates is a dict of user fields to change. It is categorised as a Write tool in the Redmine MCP OAuth Server 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_user? +

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

What risk level is update_user? +

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

Can I rate-limit update_user? +

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

How do I block update_user completely? +

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

What MCP server provides update_user? +

update_user is provided by the Redmine MCP OAuth Server MCP server (zh/redmine_mcp_py). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.