// SCAN REPORT

Backlog MCP Server

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 12 Jun 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 12/06/2026

How to control Backlog MCP Server ↓

TOOL MAP

What Backlog MCP Server exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Backlog MCP Server tools

Write · Medium updateIssue This tool creates or modifies data reversibly by updating issue records in Backlog.

1 of Backlog MCP Server's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Backlog MCP Server

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

Rate limit write operations

{
  "updateIssue": {
    "limits": [
      {
        "counter": "updateissue_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "getIssue": {
    "limits": [
      {
        "counter": "getissue_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 Backlog MCP Server — 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 BACKLOG →

Free to start. No card required.

FULL CATALOGUE

All 4 Backlog MCP Server tools

WRITE 1 tools

Write updateIssue Backlog課題を更新します

READ 3 tools

Read getIssue 特定のBacklog課題を取得します Read getProjects Backlogのプロジェクト一覧を取得します Read searchIssues Backlogの課題を検索します

FAQ

Questions about Backlog MCP Server

How do I prevent bulk modifications through Backlog MCP Server? +

The Backlog MCP Server server has 1 write tools including updateIssue. 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 Backlog MCP Server.

How many tools does the Backlog MCP Server MCP server expose? +

4 tools across 2 categories: Read, Write. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Backlog MCP Server? +

Register the Backlog MCP Server 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 Backlog MCP Server tool call.

Deterministic rules across all 4 Backlog MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BACKLOG →

Free to start. No card required.

4 Backlog MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.