confluence_upload_attachment · Jira MCP Server MCP

WHAT IT DOES

What confluence_upload_attachment does on Jira MCP Server

AI agents use confluence_upload_attachment to create or update resources in Jira MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira MCP Server environment.

WHY IT NEEDS A POLICY

Why confluence_upload_attachment needs a policy

This tool creates new attachment objects within Confluence pages, which is a reversible write operation. Files can be deleted or replaced later. The severity is medium because while uploads are modifiable, they can introduce security risks if malicious files are uploaded (e.g., executables, malware) or if sensitive data is inadvertently exposed via the Confluence system.

From the tool's definition Tool name 'confluence_upload_attachment' and description 'Upload a file as an attachment to a Confluence page' directly indicates file creation/addition to a Confluence page.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confluence_upload_attachment Rate-limited

confluence_upload_attachment 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "confluence_upload_attachment": {
      "limits": [
        {
          "counter": "confluence_upload_attachment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jira MCP Server, so you can run agents against it safely.

FAQ

Questions about confluence_upload_attachment

What does the confluence_upload_attachment tool do? +

Upload a file as an attachment to a Confluence page. Provide either filePath or fileContent (base64) + fileName. It is categorised as a Write tool in the Jira MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on confluence_upload_attachment? +

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

What risk level is confluence_upload_attachment? +

confluence_upload_attachment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit confluence_upload_attachment? +

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

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

confluence_upload_attachment is provided by the Jira MCP Server MCP server (rui-branco/jira-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.