Delete a footer comment in Confluence (API v2)
AI agents call deleteFooterComment to permanently remove resources in MCP Atlassian Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on Confluence footer comments. While the blast radius is constrained to comment deletion rather than critical infrastructure, unauthorized deletion of comments could compromise audit trails, discussion history, and collaborative documentation.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a footer comment in Confluence'; this action irreversibly removes data.
Documented attack patterns abuse exactly the kind of access deleteFooterComment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Atlassian Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteFooterComment:
{
"version": "1",
"default": "deny",
"hide": [
"deleteFooterComment"
]
}deleteFooterComment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a footer comment in Confluence (API v2). It is categorised as a Destructive tool in the MCP Atlassian Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Atlassian Server MCP server in PolicyLayer and add a rule for deleteFooterComment: 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 MCP Atlassian Server. Nothing to install.
deleteFooterComment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteFooterComment 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 deleteFooterComment. 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.
deleteFooterComment is provided by the MCP Atlassian Server MCP server (phuc-nt/mcp-atlassian-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 MCP Atlassian Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 MCP Atlassian Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.