create_content_fragment · Dust MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_content_fragment does on Dust MCP Server

AI agents use create_content_fragment 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 create_content_fragment needs a policy

This tool creates new content fragments within the Dust workspace. Write operations that create data are reversible (fragments can be updated or deleted later), making this a Write category risk rather than Execute or higher. Severity is medium because uncontrolled creation could lead to workspace pollution, but the impact is limited to data creation without executing arbitrary code or causing irreversible damage.

From the tool's definition Tool name 'create_content_fragment' and description 'Create a content fragment' indicate data creation. The verb 'create' is a Write operation that adds new data to the system reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_content_fragment Rate-limited

create_content_fragment 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": {
    "create_content_fragment": {
      "limits": [
        {
          "counter": "create_content_fragment_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 create_content_fragment

What does the create_content_fragment tool do? +

Create a content fragment. 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 create_content_fragment? +

Register the Dust MCP Server MCP server in PolicyLayer and add a rule for create_content_fragment: 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 create_content_fragment? +

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

Can I rate-limit create_content_fragment? +

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

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

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