Get footer comments on a page. Returns comments with their content and metadata.
AI agents call confluence_get_comments to retrieve information from Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves and returns comments from a Confluence page. It has no capability to create, modify, delete, or execute operations. The blast radius of misuse is minimal—an AI agent could retrieve comments it shouldn't see, but cannot alter or damage data. This is a straightforward Read category tool.
From the tool's definition Tool name 'confluence_get_comments' and description 'Get footer comments on a page. Returns comments with their content and metadata' indicate retrieval of existing data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access confluence_get_comments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for confluence_get_comments:
{
"version": "1",
"default": "deny",
"tools": {
"confluence_get_comments": {}
}
}confluence_get_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get footer comments on a page. Returns comments with their content and metadata. It is categorised as a Read tool in the Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Atlassian MCP server in PolicyLayer and add a rule for confluence_get_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 Atlassian. Nothing to install.
confluence_get_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the confluence_get_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.
Set action: deny in the PolicyLayer policy for confluence_get_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.
confluence_get_comments is provided by the Atlassian MCP server (xuanxt/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
51 Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.