agents_trigger_create
Create a new trigger for an AI agent. Triggers determine when the agent activates. Trigger types: - incoming_message: Activates on new incoming messages - schedule: Activates on a schedule - webhook: Activates on webhook events - event: Activates on system events
This record as markdown: /tools/io-github-saloprj-dialogbrain/agents-trigger-create.md
What agents_trigger_create does on Dialogbrain
AI agents use agents_trigger_create 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 | — | Whether the trigger is enabled. OMIT to use the default (true). |
agent_id | integer | Yes | ID of the agent to create a trigger for |
priority | integer | — | Trigger priority — lower numbers run first (default: 100) |
send_mode | string | — | Send mode override for this trigger. OMIT to inherit from the agent. |
conditions | object | — | Trigger conditions (JSON). Supported fields for incoming_message: - keywords: ["pricing","demo"] — message must contain keyword(s) (free, no LLM cost) - keyword |
thread_ids | array | — | Restrict this trigger to specific threads (chats) by their numeric thread IDs. When set, the trigger only fires for messages in these threads. Only for incoming |
trigger_type | string | Yes | Type of trigger: 'incoming_message', 'incoming_call', 'schedule', 'webhook', 'event', 'blockchain_event', 'job_completed', or 'calendar_event' |
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, even |
Parameters from the server's own tool schema.
Why agents_trigger_create is rated Medium
This tool creates a new trigger configuration that controls when an AI agent activates. It is a Write operation (reversible creation of a configuration object). However, severity is high because misconfigured triggers could cause AI agents to activate unintendedly on incoming messages, schedules, webhooks, or system events — potentially leading to unauthorized message sending or other agent actions at scale across…
From the tool's definition Create a new trigger for an AI agent. Triggers determine when the agent activates.
Attacks that exploit this kind of access
The rule that runs agents_trigger_create 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_create, this is the rule to start with:
agents_trigger_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every agents_trigger_create call is checked against it from then on.
Questions about agents_trigger_create
Create a new trigger for an AI agent. Triggers determine when the agent activates. Trigger types: - incoming_message: Activates on new incoming messages - schedule: Activates on a schedule - webhook: Activates on webhook events - event: Activates on system events. 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.
agents_trigger_create accepts 8 parameters: enabled, agent_id, priority, send_mode, conditions, thread_ids, trigger_type, excluded_thread_ids. Required: agent_id, trigger_type. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for agents_trigger_create: 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.
agents_trigger_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the agents_trigger_create 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.
Set action: deny in the PolicyLayer policy for agents_trigger_create. 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.
agents_trigger_create 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.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue