agents_set_integration
Enable or disable a connected workspace integration on an AI agent — this controls which ext<id>_<name> integration tools the agent (and its sandboxed workbench runs) may call. Use integrations_list to get the workspace_integration_id. When enabling with no explicit denied_tools, WRITE-class tool...
This record as markdown: /tools/io-github-saloprj-dialogbrain/agents-set-integration.md
What agents_set_integration does on Dialogbrain
AI agents use agents_set_integration 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 |
|---|---|---|---|
enabled | boolean | — | True to enable the integration on this agent, False to disable |
agent_id | integer | Yes | ID of the agent to configure |
denied_tools | array | — | Optional explicit block-list of tool names to deny (ext slugs or bare names). Omit to auto-deny WRITE-class tools on first enable; pass [] to allow all. |
workspace_integration_id | integer | Yes | ID of the connected integration (from integrations_list) |
Parameters from the server's own tool schema.
Why agents_set_integration is rated Medium
This tool modifies agent permissions and integration settings, allowing or blocking access to external tools/integrations. While it doesn't delete data or execute arbitrary operations, it is a Write operation that changes agent behavior and capabilities in a material way.
From the tool's definition Tool description states it "Enable or disable a connected workspace integration on an AI agent" and "controls which...integration tools the agent...may call." This modifies agent configuration and permissions settings, which are reversible configuration…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs agents_set_integration 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 agents_set_integration, this is the rule to start with:
agents_set_integration 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 agents_set_integration call is checked against it from then on.
Questions about agents_set_integration
Enable or disable a connected workspace integration on an AI agent — this controls which ext<id>_<name> integration tools the agent (and its sandboxed workbench runs) may call. Use integrations_list to get the workspace_integration_id. When enabling with no explicit denied_tools, WRITE-class tools are auto-disabled by default (read tools stay on); pass denied_tools=[] to force-allow everything, or a list of ext slugs / bare tool names to block specific ones. Idempotent upsert — safe to call repeatedly. 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.
agents_set_integration accepts 4 parameters: enabled, agent_id, denied_tools, workspace_integration_id. Required: agent_id, workspace_integration_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 agents_set_integration: 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.
agents_set_integration 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 agents_set_integration 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 agents_set_integration. 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.
agents_set_integration 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