update_membership · Redmine MCP: Risk & Policy | PolicyLayer

WHAT IT DOES

What update_membership does on Redmine

AI agents use update_membership 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_membership needs a policy

The tool updates (modifies) roles within an existing membership record. This is a Write operation because it changes data in a reversible manner. Severity is medium because modifying user roles in a project management system like Redmine could affect access control and team permissions, but the change can be undone by updating roles again.

From the tool's definition Tool description states 'Update roles for an existing membership' - this modifies membership data reversibly without deleting it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_membership Rate-limited

update_membership 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_membership": {
      "limits": [
        {
          "counter": "update_membership_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_membership

What does the update_membership tool do? +

Update roles for an existing membership. 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_membership? +

Register the Redmine MCP server in PolicyLayer and add a rule for update_membership: 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_membership? +

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

Can I rate-limit update_membership? +

Yes. Add a rate_limit block to the update_membership 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_membership completely? +

Set action: deny in the PolicyLayer policy for update_membership. 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_membership? +

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