Low Risk

confluence_get_page_labels

Get labels on a Confluence page

How to control confluence_get_page_labels ↓

AI agents call confluence_get_page_labels 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 metadata (labels) from an existing Confluence page. It performs a query/fetch operation that does not create, modify, delete, or execute anything. The action is purely informational and read-only, making it a Read category tool with low severity since label retrieval poses minimal risk even if an AI agent calls it with arbitrary page identifiers.

From the tool's definition Tool name 'confluence_get_page_labels' and description 'Get labels on a Confluence page' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access confluence_get_page_labels 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_get_page_labels:

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

confluence_get_page_labels 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_get_page_labels tool do? +

Get labels 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_get_page_labels? +

Register the Sage MCP server in PolicyLayer and add a rule for confluence_get_page_labels: 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_get_page_labels? +

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

Can I rate-limit confluence_get_page_labels? +

Yes. Add a rate_limit block to the confluence_get_page_labels 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_get_page_labels completely? +

Set action: deny in the PolicyLayer policy for confluence_get_page_labels. 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_get_page_labels? +

confluence_get_page_labels 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.