Low Risk

confluence_get_page

Get a Confluence page by ID, including its body content.

How to control confluence_get_page ↓

AI agents call confluence_get_page to retrieve information from autoMate 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 and queries Confluence page data without side effects. It matches the Read category pattern of fetching existing information. Severity is low because reading pages poses minimal risk; the blast radius of accidental misuse is limited to information disclosure, which is less damaging than write, execute, or destructive operations.

From the tool's definition Tool name includes 'get' and description states 'Get a Confluence page by ID, including its body content' — pure retrieval with no modification or deletion.

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

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

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

confluence_get_page 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 autoMate — 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 tool do? +

Get a Confluence page by ID, including its body content. It is categorised as a Read tool in the autoMate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on confluence_get_page? +

Register the autoMate MCP server in PolicyLayer and add a rule for confluence_get_page: 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 autoMate. Nothing to install.

What risk level is confluence_get_page? +

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

Can I rate-limit confluence_get_page? +

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

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

confluence_get_page is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every autoMate tool call.

Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

128 autoMate 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.