ai_tags_add_to_thread
Apply one or more AI tags to a thread (manually). When to use: - User wants to label a conversation with one or more tags - User asks to categorize or tag a thread Provide the thread_id (integer) and an array of tag_ids to apply. If a tag is already applied it will be updated to is_manual=true.
This record as markdown: /tools/io-github-saloprj-dialogbrain/ai-tags-add-to-thread.md
What ai_tags_add_to_thread does on Dialogbrain
AI agents use ai_tags_add_to_thread 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 |
|---|---|---|---|
tag_ids | array | Yes | Array of tag IDs to apply (1–20 IDs) |
thread_id | integer | Yes | ID of the thread to tag |
Parameters from the server's own tool schema.
Why ai_tags_add_to_thread is rated Medium
This tool creates or modifies labels/tags on a thread (categorization metadata). The description indicates it applies tags and updates is_manual flags, which are reversible write operations. The blast radius is minimal—an AI agent misuse would result in incorrect thread categorization, not data loss or external side effects. This fits the Write category: creates or modifies data reversibly.
From the tool's definition Apply one or more AI tags to a thread (manually). The tool modifies thread metadata by adding/updating tags without deleting or reversing prior state.
Attacks that exploit this kind of access
The rule that runs ai_tags_add_to_thread 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_add_to_thread, this is the rule to start with:
ai_tags_add_to_thread 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 ai_tags_add_to_thread call is checked against it from then on.
Questions about ai_tags_add_to_thread
Apply one or more AI tags to a thread (manually). When to use: - User wants to label a conversation with one or more tags - User asks to categorize or tag a thread Provide the thread_id (integer) and an array of tag_ids to apply. If a tag is already applied it will be updated to is_manual=true. 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.
ai_tags_add_to_thread accepts 2 parameters: tag_ids, thread_id. Required: tag_ids, thread_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_add_to_thread: 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_add_to_thread 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 ai_tags_add_to_thread 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_add_to_thread. 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_add_to_thread 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