Low Risk

confluence_list_page_comments

Get footer comments on a Confluence page

How to control confluence_list_page_comments ↓

AI agents call confluence_list_page_comments to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves existing comments from a Confluence page. It performs a read-only query operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an attacker could only view comments that may already be accessible through normal Confluence permissions. No sensitive operations or destructive capability is present.

From the tool's definition Tool name includes 'list' and description states 'Get footer comments' — both indicate data retrieval with no modification or side effects.

Documented attack patterns abuse exactly the kind of access confluence_list_page_comments gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for confluence_list_page_comments:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "confluence_list_page_comments": {}
  }
}

confluence_list_page_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the confluence_list_page_comments tool do? +

Get footer comments on a Confluence page. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on confluence_list_page_comments? +

Register the Sage MCP server in PolicyLayer and add a rule for confluence_list_page_comments: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Sage MCP. Nothing to install.

What risk level is confluence_list_page_comments? +

confluence_list_page_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit confluence_list_page_comments? +

Yes. Add a rate_limit block to the confluence_list_page_comments rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block confluence_list_page_comments completely? +

Set action: deny in the PolicyLayer policy for confluence_list_page_comments. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides confluence_list_page_comments? +

confluence_list_page_comments is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sage MCP tool call.

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

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ 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.