owners_remove
Unregister a business owner — removes the contact from the Assistant's restriction trigger (sender_filter). Fails with not_found if the contact is not currently an owner.
This record as markdown: /tools/io-github-saloprj-dialogbrain/owners-remove.md
What owners_remove does on Dialogbrain
AI agents use owners_remove 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 |
|---|---|---|---|
channel | string | — | Channel the contact belongs to. OMIT to use the default ('telegram'). |
contact | string | Yes | Owner contact to remove (@username, numeric id, or phone). |
Parameters from the server's own tool schema.
Why owners_remove is rated Medium
This tool removes a contact from an access-control list (sender_filter), which is a reversible write/modification operation — the owner can presumably be re-added. However, misuse could grant unintended access by removing legitimate restriction triggers, giving it medium severity.
From the tool's definition Unregister a business owner — removes the contact from the Assistant's restriction trigger (sender_filter)
Attacks that exploit this kind of access
The rule that runs owners_remove 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 owners_remove, this is the rule to start with:
owners_remove 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 owners_remove call is checked against it from then on.
Questions about owners_remove
Unregister a business owner — removes the contact from the Assistant's restriction trigger (sender_filter). Fails with not_found if the contact is not currently an owner. 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.
owners_remove accepts 2 parameters: channel, contact. Required: contact. 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 owners_remove: 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.
owners_remove 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 owners_remove 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 owners_remove. 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.
owners_remove 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