create_conversation · Dust MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_conversation does on Dust MCP Server

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

This tool creates a new conversation object, which is a data creation operation. While conversations may be stored persistently, they can typically be deleted or archived (making them reversible), and there are no irreversible deletions, financial transfers, or arbitrary code execution involved. The blast radius is limited to creating a new conversation session.

From the tool's definition Tool name 'create_conversation' and description 'Start a new conversation' indicate creation of a new messaging session entity within the Dust platform workspace. This is a reversible write operation that creates data structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_conversation Rate-limited

create_conversation 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_conversation": {
      "limits": [
        {
          "counter": "create_conversation_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_conversation

What does the create_conversation tool do? +

Start a new conversation. 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_conversation? +

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

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

Can I rate-limit create_conversation? +

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

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

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