agents_trigger_delete
Delete a trigger from an AI agent. WARNING: This cannot be undone.
This record as markdown: /tools/io-github-saloprj-dialogbrain/agents-trigger-delete.md
What agents_trigger_delete does on Dialogbrain
AI agents call agents_trigger_delete to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | integer | Yes | ID of the agent that owns this trigger |
trigger_id | integer | Yes | ID of the trigger to delete |
Parameters from the server's own tool schema.
Why agents_trigger_delete is rated Critical
The tool permanently removes a trigger (a condition or event that activates AI agent behavior) with no undo capability. While not directly deleting user data, removing agent triggers irreversibly alters system behavior and cannot be recovered, meeting the Destructive category definition.
From the tool's definition Tool name 'agents_trigger_delete' combined with description stating 'Delete a trigger from an AI agent' and explicit warning 'This cannot be undone' indicates irreversible deletion of agent configuration.
Attacks that exploit this kind of access
The rule that runs agents_trigger_delete 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_delete, this is the rule to start with:
agents_trigger_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every agents_trigger_delete call is checked against it from then on.
Questions about agents_trigger_delete
Delete a trigger from an AI agent. WARNING: This cannot be undone. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
agents_trigger_delete accepts 2 parameters: agent_id, trigger_id. Required: agent_id, trigger_id. 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_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the agents_trigger_delete 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_delete. 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_delete 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.
Across the catalogue