// SCAN REPORT

Redmine

32 tools. 13 can modify or destroy data without limits.

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

Last updated: 29 Jun 2026

13 can modify or destroy data

19 read-only

32 tools total

Community server · catalogue entry verified 29/06/2026

How to control Redmine ↓

TOOL MAP

What Redmine exposes to your agents

Read (19) Write / Execute (9) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Redmine tools

Destructive · High redmine_delete_wiki_page This tool irreversibly deletes wiki page data with no recovery mechanism. Destructive · High delete_issue_relation The tool irreversibly deletes data (issue relations) and explicitly states the action cannot be undone. Destructive · High redmine_delete_issue The tool irreversibly deletes data (issue, journals, attachments) with no undo capability. Destructive · High redmine_delete_time_entry This tool irreversibly deletes data (time entries) with no undo mechanism.

13 of Redmine's 32 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_issue_relation": {
    "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

{
  "create_issue_relation": {
    "limits": [
      {
        "counter": "create_issue_relation_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_issue_relation": {
    "limits": [
      {
        "counter": "get_issue_relation_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 32 Redmine tools

DESTRUCTIVE 4 tools

Destructive delete_issue_relation [Alpha] Permanently delete a Redmine issue relation by its numeric ID. This action cannot be undone. Destructive redmine_delete_issue [Stable] Permanently delete a Redmine issue and all its journals and attachments. This action cannot be undone Destructive redmine_delete_time_entry [Stable] Permanently delete a Redmine time entry. This action cannot be undone. Destructive redmine_delete_wiki_page [Alpha] Permanently delete a Redmine wiki page. Requires admin privileges. This action cannot be undone.

WRITE 9 tools

Write create_issue_relation [Alpha] Create a relation between two Redmine issues. Supported types: relates, duplicates, duplicated, blocks Write redmine_create_issue [Stable] Create a new Redmine issue. Returns the created issue with its assigned ID. Write redmine_create_project [Stable] Create a new Redmine project. Returns the created project. Write redmine_log_time [Stable] Log time against a Redmine issue or project. Either issue_id or project_id is required. Returns the c Write redmine_update_issue [Stable] Update an existing Redmine issue. Only provided fields are changed. Use Write redmine_update_project [Stable] Update an existing Redmine project. Only provided fields are changed. Write redmine_update_time_entry [Stable] Update an existing Redmine time entry. Only provided fields are changed. Write redmine_update_wiki_page [Alpha] Create or update a Redmine wiki page. If the page does not exist, it will be created. IMPORTANT: Alway Write redmine_upload_file [Alpha] Upload a file to a Redmine project. IMPORTANT: You must first upload the file using Redmine

READ 19 tools

Read get_issue_relation [Alpha] Get a single Redmine issue relation by its numeric ID. Read list_issue_relations [Alpha] List all relations for a given Redmine issue. Returns each relation Read redmine_get_current_user [Stable] Get the details of the currently authenticated Redmine user (identified by REDMINE_API_KEY). Read redmine_get_issue [Stable] Get full details of a single Redmine issue by its numeric ID, including description, status, dates, a Read redmine_get_my_account [Stable] Get the full account details of the currently authenticated Redmine user, including email address, AP Read redmine_get_project [Stable] Get details of a single Redmine project by its identifier (string slug) or numeric ID. Read redmine_get_role [Alpha] Get detailed information about a role including permissions, visibility settings, and assignability (r Read redmine_get_time_entry [Stable] Get details of a single time entry by its numeric ID. Read redmine_get_user [Stable] Get details of a single Redmine user by numeric ID. Read redmine_get_wiki_page [Alpha] Get the content and metadata of a Redmine wiki page by project and page title. Read redmine_list_files [Alpha] List all files in a Redmine project. Returns file metadata including name, size, type, author, and dow Read redmine_list_issues [Stable] List Redmine issues with optional filters. Returns paginated results with issue ID, subject, status, Read redmine_list_news [Alpha] List Redmine news articles. Returns paginated results with title, summary, author, project, and creati Read redmine_list_projects [Stable] List all Redmine projects the API user has access to, with pagination support. Read redmine_list_roles [Alpha] List all roles in the Redmine instance. Returns role IDs and names for role assignment. Read redmine_list_time_entries [Stable] List Redmine time entries with optional filters. Returns hours logged, activity, issue, and project f Read redmine_list_users [Stable] List Redmine users. Requires admin privileges. Returns user IDs, login names, and email addresses. Read redmine_list_wiki_pages [Alpha] List all wiki pages in a Redmine project. Read redmine_search [Alpha] Search Redmine content across issues, wiki pages, news, documents, changesets, messages, projects, and

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 4 destructive tools including delete_issue_relation, redmine_delete_issue, redmine_delete_time_entry. 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 9 write tools including create_issue_relation, redmine_create_issue, redmine_create_project. 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? +

32 tools across 3 categories: Destructive, Read, Write. 19 are read-only. 13 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 32 Redmine tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON REDMINE →

Instant setup, no code required.

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