ai_tags_list
List all personal AI tags. AI tags are automatic message filters: the system runs a lightweight classifier on every incoming message and applies matching tags to threads. This lets AI agents skip expensive full analysis on most messages — they only act on threads that match relevant tags, dramati...
This record as markdown: /tools/io-github-saloprj-dialogbrain/ai-tags-list.md
What ai_tags_list does on Dialogbrain
AI agents call ai_tags_list to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ai_tags_list is rated Low
This tool retrieves metadata about existing message classification tags and their associated thread counts. It performs a pure query operation with no side effects — no messages are sent, no data is modified, and no external actions are triggered. This is a straightforward Read operation.
From the tool's definition Tool name 'ai_tags_list' and description explicitly state 'List all personal AI tags' with return of 'all tags with thread counts'. The description uses read-only verbs: 'Check', 'Get', 'See'.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs ai_tags_list 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_list, this is the rule to start with:
ai_tags_list is read-only, so it stays allowed. 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_list call is checked against it from then on.
Questions about ai_tags_list
List all personal AI tags. AI tags are automatic message filters: the system runs a lightweight classifier on every incoming message and applies matching tags to threads. This lets AI agents skip expensive full analysis on most messages — they only act on threads that match relevant tags, dramatically cutting LLM costs. When to use: - Check which auto-classification filters exist before creating one - Get tag IDs for add_to_thread / remove_from_thread - See how many threads each tag currently matches Returns all tags with thread counts (non-archived, included threads only). It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for ai_tags_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ai_tags_list 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_list. 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_list 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