agents_list_integrations
List the workspace integrations enabled (or available) for an AI agent, with each one's workspace_integration_id, provider, enabled flag, and count of denied tools. Use this to see what an agent can call before toggling with agents_set_integration.
This record as markdown: /tools/io-github-saloprj-dialogbrain/agents-list-integrations.md
What agents_list_integrations does on Dialogbrain
AI agents call agents_list_integrations 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_id | integer | Yes | ID of the agent to inspect |
Parameters from the server's own tool schema.
Why agents_list_integrations is rated Low
This tool performs a query/retrieval operation with no side effects. It returns read-only information about integrations to inform the user before making changes via agents_set_integration. The blast radius of misuse is minimal—an attacker learns what integrations are available, which is informational and non-destructive.
From the tool's definition Tool description states it "List[s] the workspace integrations enabled (or available)" and retrieves integration metadata (workspace_integration_id, provider, enabled flag, denied tool counts).
Attacks that exploit this kind of access
The rule that runs agents_list_integrations 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_list_integrations, this is the rule to start with:
agents_list_integrations 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 agents_list_integrations call is checked against it from then on.
Questions about agents_list_integrations
List the workspace integrations enabled (or available) for an AI agent, with each one's workspace_integration_id, provider, enabled flag, and count of denied tools. Use this to see what an agent can call before toggling with agents_set_integration. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
agents_list_integrations accepts 1 parameter: agent_id. Required: agent_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_list_integrations: 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_list_integrations 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 agents_list_integrations 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_list_integrations. 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_list_integrations 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