integrations_list

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/integrations-list.md

WHAT IT DOES

What integrations_list does on Dialogbrain

AI agents call integrations_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.

RISK

Why integrations_list is rated Low

This tool retrieves and queries configuration data about integrations without creating, modifying, deleting, or executing operations. It is a straightforward information retrieval operation with no side effects. The low severity reflects minimal blast radius—an AI agent misuse would only expose integration metadata and configuration details, not trigger external actions or cause data loss.

From the tool's definition Tool description uses 'List' and explicitly describes retrieval: 'List the workspace's external integrations...each with its id, provider name, base_url, transport, status, and registered tool count.' No modification, deletion, or execution of external…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs integrations_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 integrations_list, this is the rule to start with:

integrations_list Allowed

integrations_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "integrations_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every integrations_list call is checked against it from then on.

FAQ

Questions about integrations_list

What does the integrations_list tool do? +

List the workspace's external integrations (HTTP-API + MCP), each with its id, provider name, base_url, transport, status, and registered tool count. Use before integrations.add_endpoints to find the integration id / base_url. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on integrations_list? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for integrations_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.

What risk level is integrations_list? +

integrations_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit integrations_list? +

Yes. Add a rate_limit block to the integrations_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.

How do I block integrations_list completely? +

Set action: deny in the PolicyLayer policy for integrations_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.

What MCP server provides integrations_list? +

integrations_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.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →