agents_trigger_update

Update an existing AI agent trigger. All parameters are optional — only provided fields will be updated.

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

Medium RISK CLASS

Category Write

Parameters 92 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/agents-trigger-update.md

WHAT IT DOES

What agents_trigger_update does on Dialogbrain

AI agents use agents_trigger_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
`enabled`	boolean	—	Enable or disable this trigger. OMIT to leave the enabled flag unchanged.
`agent_id`	integer	Yes	ID of the agent that owns this trigger
`priority`	integer	—	Trigger priority — lower numbers run first
`send_mode`	string	—	New send mode override. OMIT to leave the send-mode unchanged.
`conditions`	object	—	New trigger conditions (replaces existing). Same fields as trigger_create: keywords, keyword_match, channel_types, context_types, group_mode, channel_account_id
`thread_ids`	array	—	Restrict this trigger to specific threads (chats) by their numeric thread IDs. When set, merged into conditions.thread_filter.thread_ids. If conditions is also
`trigger_id`	integer	Yes	ID of the trigger to update
`trigger_type`	string	—	New trigger type. OMIT to keep the existing type unchanged.
`excluded_thread_ids`	array	—	Exclude specific threads (chats) by their numeric thread IDs — the opposite of thread_ids. When set, the trigger NEVER fires for messages in these threads (expl

Parameters from the server's own tool schema.

RISK

Why agents_trigger_update is rated Medium

This tool modifies an existing AI agent trigger configuration. It's a reversible write operation (the trigger can be updated again), but misuse could cause agents to behave unexpectedly — e.g., triggering on wrong conditions, silencing important alerts, or misdirecting message routing across WhatsApp, Telegram, Email, or voice channels.

From the tool's definition Update an existing AI agent trigger

Attacks that exploit this kind of access

RECOMMENDED RULE

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

agents_trigger_update Rate-limited

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

FAQ

Questions about agents_trigger_update

What does the agents_trigger_update tool do? +

Update an existing AI agent trigger. All parameters are optional — only provided fields will be 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 agents_trigger_update accept? +

agents_trigger_update accepts 9 parameters: enabled, agent_id, priority, send_mode, conditions, thread_ids, trigger_id, trigger_type, excluded_thread_ids. Required: agent_id, trigger_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on agents_trigger_update? +

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

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

Can I rate-limit agents_trigger_update? +

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

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

agents_trigger_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_register_agents on Team Manager MCP → The MCP Attack Database →

Guides

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