threads_update

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

Medium RISK CLASS

Category Write

Parameters 51 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/threads-update.md

WHAT IT DOES

What threads_update does on Dialogbrain

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

Parameter	Type	Required	Description
`title`	string	—	New title for the thread (max 255 chars)
`folder_id`	integer	—	Move thread to this folder (null removes from folder)
`thread_id`	string	Yes	Thread ID from threads.list
`description`	string	—	AI context / notes for this thread. Empty string clears description.
`update_contact`	boolean	—	For DM threads, also rename the linked contact (default: true)

Parameters from the server's own tool schema.

RISK

Why threads_update is rated Medium

This tool modifies existing data reversibly without deleting or executing arbitrary code. Updates to thread names, descriptions, and folder organization are typical Write operations. Severity is medium because unintended modifications could disrupt conversation organization and context (e.g., renaming a DM also updates the contact's display name by default), affecting multiple users, but changes are reversible.

From the tool's definition Tool updates conversation metadata (rename, add notes/description, move to folder). Description explicitly states "✏️ Update" and lists modification operations: rename, add notes/description, organize into folders.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs threads_update safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For threads_update, this is the rule to start with:

threads_update Rate-limited

threads_update 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": {
    "threads_update": {
      "limits": [
        {
          "counter": "threads_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every threads_update call is checked against it from then on.

FAQ

Questions about threads_update

What does the threads_update tool do? +

✏️ Update a conversation thread: rename it, add notes/description, or move to a folder. When to use: - User wants to rename a chat or group - User wants to add notes/context about a conversation - User wants to organize threads into folders For DM threads, renaming also updates the linked contact's display name by default. Requires thread_id from threads.list. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does threads_update accept? +

threads_update accepts 5 parameters: title, folder_id, thread_id, description, update_contact. Required: thread_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on threads_update? +

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

What risk level is threads_update? +

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

Can I rate-limit threads_update? +

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

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

threads_update is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →