Medium Risk

replace_document_by_id

Replace an existing document by ID

Risk signalsOverwrites entire document content

Part of the Couchbase server.

replace_document_by_id can modify Couchbase data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE COUCHBASE →

Free to start. No card required.

AI agents use replace_document_by_id to create or modify resources in Couchbase. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call replace_document_by_id repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Couchbase.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "replace_document_by_id": {
      "limits": [
        {
          "counter": "replace_document_by_id_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Couchbase policy for all 23 tools.

Get this rule live on your own Couchbase server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY COUCHBASE →

View all 23 tools →

These attack patterns abuse exactly the kind of access replace_document_by_id gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so replace_document_by_id only ever does what you allow.

SECURE COUCHBASE →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the replace_document_by_id tool do? +

Replace an existing document by ID. It is categorised as a Write tool in the Couchbase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on replace_document_by_id? +

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

What risk level is replace_document_by_id? +

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

Can I rate-limit replace_document_by_id? +

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

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

replace_document_by_id is provided by the Couchbase MCP server (@couchbase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Couchbase tool call.

Deterministic rules across all 23 Couchbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.