prompts_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/prompts-update.md

WHAT IT DOES

What prompts_update does on Dialogbrain

AI agents use prompts_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 name for the prompt template
`prompt_id`	integer	Yes	ID of the prompt template to update
`description`	string	—	New description for the prompt template
`prompt_text`	string	—	The AI system prompt: persona, tone, rules, behavior.
`auto_reply_rules`	string	—	Pre-classifier rules that run BEFORE the main AI. Format: bullet list of conditions → actions (SKIP / SIMPLE_REPLY / SEARCH / CALENDAR). Pass null to clear.

Parameters from the server's own tool schema.

RISK

Why prompts_update is rated Medium

This tool modifies prompt templates that affect every agent using that template. While reversible (making it Write rather than Destructive), the scope of impact is high: changing system instructions or auto-reply rules across multiple agents could cause widespread behavioral changes, miscommunications, or unintended agent actions. The blast radius justifies high severity despite the Write category.

From the tool's definition Tool explicitly performs 'Update' operations on 'prompt template's name, system instructions, or auto-reply rules.' The description states 'only provided fields are updated,' indicating reversible modification of data.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

prompts_update Rate-limited

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

FAQ

Questions about prompts_update

What does the prompts_update tool do? +

Update a prompt template's name, system instructions, or auto-reply rules. Changes affect every agent using this template, unless the agent has its own override (set via agents.update → prompt_text). All parameters except prompt_id are optional — only provided fields are updated. 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 prompts_update accept? +

prompts_update accepts 5 parameters: name, prompt_id, description, prompt_text, auto_reply_rules. Required: prompt_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on prompts_update? +

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

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

Can I rate-limit prompts_update? +

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

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

prompts_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 →