save_attachment_metadata · Bitbucket Server MCP

WHAT IT DOES

What save_attachment_metadata does on Bitbucket Server MCP

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

WHY IT NEEDS A POLICY

Why save_attachment_metadata needs a policy

The 'save' operation creates or updates attachment metadata, making this a Write action. While the description is empty, the context of a Bitbucket Server MCP with attachment handling supports this classification.

From the tool's definition Tool name 'save_attachment_metadata' indicates creation or modification of metadata associated with attachments. The verb 'save' implies a write operation that persists data. No deletion or destructive language is present.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_attachment_metadata Rate-limited

save_attachment_metadata 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": {
    "save_attachment_metadata": {
      "limits": [
        {
          "counter": "save_attachment_metadata_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 Bitbucket Server MCP, so you can run agents against it safely.

FAQ

Questions about save_attachment_metadata

What does the save_attachment_metadata tool do? +

save_attachment_metadata. It is categorised as a Write tool in the Bitbucket Server MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_attachment_metadata? +

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

What risk level is save_attachment_metadata? +

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

Can I rate-limit save_attachment_metadata? +

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

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

save_attachment_metadata is provided by the Bitbucket Server MCP server (manpreetshuann/bitbucket-server-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.