// SCAN REPORT

Awesome Confluence

3 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 30 Jun 2026

0 can modify or destroy data

3 read-only

3 tools total

Community server · catalogue entry verified 30/06/2026

How to control Awesome Confluence ↓

TOOL MAP

What Awesome Confluence exposes to your agents

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

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Awesome Confluence

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

Cap read operations

{
  "fetch_page_markdown": {
    "limits": [
      {
        "counter": "fetch_page_markdown_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 Awesome Confluence — 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 AWESOME CONFLUENCE →

Instant setup, no code required.

FULL CATALOGUE

All 3 Awesome Confluence tools

READ 3 tools

Read fetch_page_markdown fetch_page_markdown Read list_spaces List all Confluence spaces accessible to the authenticated user. Read search_pages search_pages

FAQ

Questions about Awesome Confluence

Is the Awesome Confluence MCP server safe to use without restrictions? +

The Awesome Confluence server is primarily read-only with 3 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Awesome Confluence MCP server expose? +

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

How do I enforce a policy on Awesome Confluence? +

Register the Awesome Confluence 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 Awesome Confluence tool call.

Deterministic rules across all 3 Awesome Confluence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON AWESOME CONFLUENCE →

Instant setup, no code required.

3 Awesome Confluence tools catalogued and risk-classified — across an index of 43,000+ MCP servers.