ai_tags_delete
Delete a personal AI tag. All thread associations are removed automatically. When to use: - User wants to permanently remove a tag they no longer need This cannot be undone. Threads are NOT deleted — they just lose this tag.
This record as markdown: /tools/io-github-saloprj-dialogbrain/ai-tags-delete.md
What ai_tags_delete does on Dialogbrain
AI agents call ai_tags_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 |
|---|---|---|---|
tag_id | integer | Yes | ID of the tag to delete |
Parameters from the server's own tool schema.
Why ai_tags_delete is rated Critical
This tool permanently deletes data (tags) without possibility of recovery, matching the Destructive category definition. While the actual thread content is preserved, the tag metadata itself is irreversibly destroyed.
From the tool's definition Tool name includes 'delete'; description explicitly states 'Delete a personal AI tag' and 'This cannot be undone.' The effect is irreversible removal of metadata.
Attacks that exploit this kind of access
The rule that runs ai_tags_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 ai_tags_delete, this is the rule to start with:
ai_tags_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 ai_tags_delete call is checked against it from then on.
Questions about ai_tags_delete
Delete a personal AI tag. All thread associations are removed automatically. When to use: - User wants to permanently remove a tag they no longer need This cannot be undone. Threads are NOT deleted — they just lose this tag. 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.
ai_tags_delete accepts 1 parameter: tag_id. Required: tag_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 ai_tags_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.
ai_tags_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 ai_tags_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 ai_tags_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.
ai_tags_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