workspace_update

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

Medium RISK CLASS

Category Write

Parameters 50 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

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

WHAT IT DOES

What workspace_update does on Dialogbrain

AI agents use workspace_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
`name`	string	—	New workspace name. Omit to leave unchanged.
`logo_url`	string	—	New workspace logo URL. Omit to leave unchanged.
`settings`	object	—	Partial settings object, MERGED into the existing workspace.settings JSONB (PATCH semantics). Only the keys you send change. Common keys: translation_glossary,
`description`	string	—	New workspace description. Omit to leave unchanged.
`workspace_id`	integer	—	Numeric workspace id to update. Omit to target the currently-routed workspace (workspace.current).

Parameters from the server's own tool schema.

RISK

Why workspace_update is rated Medium

workspace_update modifies workspace configuration and metadata in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). It requires ADMIN role, which shows it's a sensitive administrative function, raising severity to high due to the blast radius of misconfiguring workspace settings across a unified communications platform.

From the tool's definition Tool description states: "Edit the active workspace (or one named by `workspace_id`): its name, description, logo_url, and/or `settings`." The verb "Edit" combined with modifiable fields (name, description, logo_url, settings) indicates creation or…

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs workspace_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 workspace_update, this is the rule to start with:

workspace_update Rate-limited

workspace_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": {
    "workspace_update": {
      "limits": [
        {
          "counter": "workspace_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 workspace_update call is checked against it from then on.

FAQ

Questions about workspace_update

What does the workspace_update tool do? +

Edit the active workspace (or one named by workspace_id): its name, description, logo_url, and/or settings. Requires ADMIN role in that workspace. settings is MERGED, not replaced — send only the keys you want to change (e.g. {"translation_glossary": "..."} or {"translation_tts_provider": "cartesia"}); other keys are left intact. Omit workspace_id to target the workspace this MCP key is currently routed to (see workspace.current). 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 workspace_update accept? +

workspace_update accepts 5 parameters: name, logo_url, settings, description, workspace_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on workspace_update? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for workspace_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 workspace_update? +

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

Can I rate-limit workspace_update? +

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

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

workspace_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 232 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 →