Redmine

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

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

Last updated:

26 can modify or destroy data
33 read-only
59 tools total

Community server · catalogue entry verified 30/06/2026

How to control Redmine ↓

What Redmine exposes to your agents

Read (33) Write / Execute (18) Destructive / Financial (8)
Critical Risk

The most dangerous Redmine tools

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

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_group": {
    "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_issue_note": {
    "limits": [
      {
        "counter": "add_issue_note_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "download_attachment": {
    "limits": [
      {
        "counter": "download_attachment_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

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

Instant setup, no code required.

All 59 Redmine tools

READ 33 tools
Read download_attachment Download an attachment and return its content as base64. Read get_attachment Get attachment metadata (filename, size, content_url, ...). Read get_group Get a group by id. include may contain: users, memberships. Read get_issue Get a single issue by id. Read get_membership Get a single membership by id. Read get_my_account Get the authenticated user's full account record (richer than Read get_project Get a single project by id or identifier. Read get_relation Get a single issue relation by id. Read get_role Get a role by id, including its permissions list. Read get_user Get a user by id, or pass the literal string 'current' for the Read get_version Get a version by id. Read get_wiki_page Get a wiki page by title. version fetches a specific revision. Read list_custom_fields List custom fields. Requires admin privileges; returns 403 otherwise. Read list_document_categories List document category enumeration values. Read list_files List files attached to a project. Read list_groups List all groups (admin only). Read list_issue_categories List issue categories for a project (id or identifier). Read list_issue_priorities List issue priority enumeration values. Read list_issue_relations List relations on an issue. Read list_issue_statuses List all issue statuses defined in the Redmine instance. Read list_issues List issues with optional filters. Read list_memberships List user/group memberships for a project. Read list_news List news entries. If project_id is None, lists across all Read list_projects List projects visible to the current user. Read list_queries List saved queries visible to the current user. Use a query's Read list_roles List all roles. Read list_time_entries List time entries. Read list_time_entry_activities List time entry activity enumeration values. Read list_trackers List all trackers (issue types) defined in the Redmine instance. Read list_users List users (admin only on most instances). Read list_versions List versions for a project. Read list_wiki_pages List wiki pages in a project. Returns the full index in one call; Read search Full-text search across Redmine.

Related servers

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

Questions about Redmine

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

Yes. The Redmine server exposes 8 destructive tools including delete_group, delete_issue, delete_relation. 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 18 write tools including add_issue_note, add_project_member, add_user_to_group. 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. 33 are read-only. 26 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.

Instant setup, no code required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.