Add a footer comment to a Confluence page
AI agents use createConfluenceFooterComment to create or update resources in Atlassian Multi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Atlassian Multi environment.
This tool creates (adds) new data in the form of a footer comment on a Confluence page. This is a reversible modification—comments can be edited or deleted—making it a Write action rather than Read (retrieves data) or Destructive (irreversible deletion).
From the tool's definition Tool name 'createConfluenceFooterComment' and description 'Add a footer comment to a Confluence page' indicate creation of new content on a Confluence page.
Attacks that exploit this kind of access
Add a footer comment to a Confluence page. It is categorised as a Write tool in the Atlassian Multi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for createConfluenceFooterComment: 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 Multi. Nothing to install.
createConfluenceFooterComment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createConfluenceFooterComment 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 createConfluenceFooterComment. 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.
createConfluenceFooterComment is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →