Add one or more labels to a page. Labels help organize and categorize content.
AI agents use confluence_add_label to create or update resources in Atlassian — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Atlassian environment.
Adding labels is a write operation that modifies page properties but does not create, delete, or execute code. The change is reversible (labels can be removed). Severity is medium because label modifications can affect content discoverability and organization, potentially impacting other users' ability to find relevant pages, but cause no data loss or irreversible damage.
From the tool's definition Tool description states 'Add one or more labels to a page,' which modifies page metadata. This is a reversible write operation that changes existing content attributes.
Documented attack patterns abuse exactly the kind of access confluence_add_label 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_add_label:
{
"version": "1",
"default": "deny",
"tools": {
"confluence_add_label": {
"limits": [
{
"counter": "confluence_add_label_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}confluence_add_label stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add one or more labels to a page. Labels help organize and categorize content. It is categorised as a Write tool in the Atlassian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Atlassian MCP server in PolicyLayer and add a rule for confluence_add_label: 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_add_label 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 confluence_add_label 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_add_label. 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_add_label 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.