// SCAN REPORT

Redmine

59 tools. 36 can modify or destroy data without limits.

12 destructive tools with no built-in limits. Policy required.

Last updated: 3 Jul 2026

36 can modify or destroy data

23 read-only

59 tools total

Community server · catalogue entry verified 03/07/2026

How to control Redmine ↓

TOOL MAP

What Redmine exposes to your agents

Read (23) Write / Execute (24) Destructive / Financial (12)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Redmine tools

Destructive · High delete_group The tool permanently removes a group from the Redmine instance, which cannot be undone. Destructive · High delete_user Deleting a user is a destructive action that cannot be undone. Destructive · High remove_user_from_group Removing a user from a group revokes their group-based permissions and access rights. Destructive · High delete_attachment The tool permanently removes an attachment from the Redmine instance without possibility of reversal (unless restored from backups outside the tool's scope).

36 of Redmine's 59 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Redmine

PolicyLayer is an MCP gateway — it sits between your AI agents and Redmine, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_attachment": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_membership": {
    "limits": [
      {
        "counter": "add_membership_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_attachment": {
    "limits": [
      {
        "counter": "get_attachment_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Redmine — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON REDMINE →

Instant setup, no code required.

FULL CATALOGUE

All 59 Redmine tools

DESTRUCTIVE 12 tools

WRITE 24 tools

Write add_membership Add a user or group to a project with specified roles. Write add_user_to_group Add a user to a group. Requires admin privileges. Write add_watcher Add a watcher to an issue. Write archive_project Archive a project. Write create_group Create a new group. Requires admin privileges. Write create_issue Create a new issue. Write create_issue_category Create a new issue category for a project. Write create_issue_relation Create a relation between two issues. Write create_or_update_wiki_page Create or update a wiki page. Redmine uses PUT for both create and update. Write create_project Create a new project. Write create_time_entry Log time spent on an issue or project. Write create_user Create a new user. Requires admin privileges. Write create_version Create a new version for a project. Write remove_watcher Remove a watcher from an issue. Write unarchive_project Unarchive a project. Write update_group Update a group. Requires admin privileges. Write update_issue Update an existing issue. Write update_issue_category Update an issue category. Write update_membership Update roles for an existing membership. Write update_project Update an existing project. Write update_time_entry Update an existing time entry. Write update_user Update a user. Requires admin privileges. Write update_version Update an existing version. Write upload_attachment Upload a file to Redmine and get a token. Use the token when creating/updating issues or wiki pages to attach

READ 23 tools

Read get_attachment Get attachment metadata by ID. Read get_current_user Get the currently authenticated user. Read get_group Get a group by ID. Requires admin privileges. Read get_issue Get a single issue by ID with full details. Read get_issue_relation Get a single issue relation by ID. Read get_project Get a single project by ID or identifier. Read get_time_entry Get a single time entry by ID. Read get_user Get a user by ID. Read get_version Get a version by ID. Read get_wiki_page Get a wiki page by project and page name. Read list_custom_fields List all custom fields. Requires admin privileges. Read list_groups List all groups. Requires admin privileges. Read list_issue_categories List all issue categories for a project. Read list_issue_relations List all relations for an issue. Read list_issue_statuses List all available issue statuses. Read list_issues List issues with optional filters and pagination. Read list_memberships List memberships for a project. Read list_projects List all accessible projects. Read list_time_entries List time entries with optional filters. Read list_trackers List all available trackers. Read list_users List users. Requires admin privileges. Read list_versions List versions for a project. Read list_wiki_pages List all wiki pages for a project.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Redmine

Can an AI agent delete data through the Redmine MCP server? +

Yes. The Redmine server exposes 12 destructive tools including delete_attachment, delete_group, delete_issue. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Redmine? +

The Redmine server has 24 write tools including add_membership, add_user_to_group, add_watcher. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Redmine.

How many tools does the Redmine MCP server expose? +

59 tools across 3 categories: Destructive, Read, Write. 23 are read-only. 36 can modify, create, or delete data.

How do I enforce a policy on Redmine? +

Register the Redmine MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Redmine tool call.

Deterministic rules across all 59 Redmine tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON REDMINE →

Instant setup, no code required.

59 Redmine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.