add_issue_watcher · Redmine MCP OAuth Server MCP

WHAT IT DOES

What add_issue_watcher does on Redmine MCP OAuth Server

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

This tool creates a new watcher association on an issue, which is a write operation that modifies data but can be reversed (watchers can be removed). It does not execute arbitrary code, delete data, move money, or retrieve sensitive information without modification. The blast radius is minimal as adding a watcher is a non-critical metadata change.

From the tool's definition Tool name 'add_issue_watcher' and description 'Add a watcher to a Redmine issue' indicate creation of a new watcher relationship, which modifies issue metadata reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_issue_watcher Rate-limited

add_issue_watcher 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": {
    "add_issue_watcher": {
      "limits": [
        {
          "counter": "add_issue_watcher_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 add_issue_watcher

What does the add_issue_watcher tool do? +

Add a watcher to a Redmine issue. 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 add_issue_watcher? +

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

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

Can I rate-limit add_issue_watcher? +

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

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

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