ai_filters_update
Update an existing AI filter's name, description, threshold, or active state. When to use: - User wants to rename a filter - User wants to refine the filter description to improve match accuracy - User wants to adjust the similarity threshold (higher = stricter matching) - User wants to enable or...
This record as markdown: /tools/io-github-saloprj-dialogbrain/ai-filters-update.md
What ai_filters_update does on Dialogbrain
AI agents use ai_filters_update 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 |
|---|---|---|---|
name | string | — | New filter name (max 100 chars, optional) |
filter_id | integer | Yes | ID of the filter to update |
is_active | boolean | — | Enable (true) or disable (false) the filter. OMIT to leave the active flag unchanged. |
threshold | number | — | New cosine similarity threshold. Range 0.1–1.0. Optional. |
description | string | — | New reference description text. If changed, the Voyage AI embedding API is called to re-generate the reference vector. Max 500 chars. Optional. |
Parameters from the server's own tool schema.
Why ai_filters_update is rated Medium
This tool modifies filter settings reversibly (rename, update description, adjust threshold, toggle active state). None of these operations delete data or produce irreversible side effects. The tool does not execute arbitrary code or move financial resources. It is clearly in the Write category as it creates or modifies data in a reversible manner.
From the tool's definition Tool description states 'Update an existing AI filter's name, description, threshold, or active state.' These are reversible modifications to filter configuration.
Attacks that exploit this kind of access
The rule that runs ai_filters_update 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_filters_update, this is the rule to start with:
ai_filters_update 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_filters_update call is checked against it from then on.
Questions about ai_filters_update
Update an existing AI filter's name, description, threshold, or active state. When to use: - User wants to rename a filter - User wants to refine the filter description to improve match accuracy - User wants to adjust the similarity threshold (higher = stricter matching) - User wants to enable or disable a filter without deleting it Provide only the fields you want to change. At least one field is required. Note: If the description is changed, this tool calls the Voyage AI embedding API to re-generate the reference vector with the new description text. 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_filters_update accepts 5 parameters: name, filter_id, is_active, threshold, description. Required: filter_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_filters_update: 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_filters_update 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_filters_update 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_filters_update. 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_filters_update 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