upsert_document · Dust MCP Server MCP: Risk & Policy

WHAT IT DOES

What upsert_document does on Dust MCP Server

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

WHY IT NEEDS A POLICY

Why upsert_document needs a policy

This tool modifies data (documents) but does so reversibly—updates can be undone and documents are not permanently destroyed. It does not execute arbitrary code, delete irreversibly, or move money. Write category is appropriate. Severity is medium because unintended document modifications in a workspace/messaging platform could affect multiple users and conversations, but the impact is recoverable.

From the tool's definition Tool name 'upsert_document' and description 'Create or update a document' indicate reversible modification of data. 'Upsert' is a standard database operation that creates a new record if it doesn't exist or updates an existing one.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upsert_document Rate-limited

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

FAQ

Questions about upsert_document

What does the upsert_document tool do? +

Create or update a document. It is categorised as a Write tool in the Dust 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 upsert_document? +

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

What risk level is upsert_document? +

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

Can I rate-limit upsert_document? +

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

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

upsert_document is provided by the Dust MCP Server MCP server (ma3u/dust-mcp-server-postman-railway). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.