integrations_add_endpoints

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

Medium RISK CLASS

Category Write

Parameters 62 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What integrations_add_endpoints does on Dialogbrain

AI agents use integrations_add_endpoints 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
`auth`	object	—	Auth block for a NEW token/header integration (or to change auth on update): {type: none\|bearer\|api_key\|basic\|custom_headers, ...}. bearer/basic → {token}; api_
`name`	string	—	Display name when creating a new integration. OMIT to default to the host.
`extract`	object	—	Explicit browser_identity auth extract for a NEW integration when auto-detect can't find one, e.g. {kind:'cookie', name:'_session', value_format:'raw', header_n
`base_url`	string	Yes	API base URL of the integration, e.g. https://api.boomnow.com
`identity`	string	—	Saved Browser Identity name or numeric id — one way to auth a NEW cookie-session integration (updates reuse existing auth). For token/header APIs use `auth` ins
`endpoints`	array	Yes	Endpoints to add. Each: {method, path, query?(object), request_body?(object sample), response_body?(object/array sample)}. path is relative to base_url, e.g. /a

Parameters from the server's own tool schema.

RISK

Why integrations_add_endpoints is rated Medium

An AI agent can call integrations_add_endpoints faster than any human can review: one bad instruction and it creates or modifies resources in Dialogbrain by the hundred, each call as confident as the last.

Risk signalsAccepts URL/endpoint input (base_url) · Handles credentials or secrets (auth)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

integrations_add_endpoints Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "integrations_add_endpoints": {
      "limits": [
        {
          "counter": "integrations_add_endpoints_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about integrations_add_endpoints

What does the integrations_add_endpoints tool do? +

Add one or more API endpoints to an HTTP-API integration as callable tools, merged additively into the integration for base_url (created if none exists). Each endpoint becomes a tool with params + request/response schemas inferred from the samples you pass. When CREATING a new integration, provide auth: either identity (saved Browser Identity name/id) for cookie-session APIs, OR an auth block for token/header APIs, e.g. {type:'bearer', token:'...'} or {type:'api_key', token:'...', header_name:'X-API-Key'}. Updates keep the existing auth unless a new auth is passed. Returns the new tool count and names. Refresh the tools list afterwards to use them. 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.

What parameters does integrations_add_endpoints accept? +

integrations_add_endpoints accepts 6 parameters: auth, name, extract, base_url, identity, endpoints. Required: base_url, endpoints. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on integrations_add_endpoints? +

Register the Dialogbrain MCP server in PolicyLayer and add a rule for integrations_add_endpoints: 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_add_endpoints? +

integrations_add_endpoints is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit integrations_add_endpoints? +

Yes. Add a rate_limit block to the integrations_add_endpoints 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_add_endpoints completely? +

Set action: deny in the PolicyLayer policy for integrations_add_endpoints. 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_add_endpoints? +

integrations_add_endpoints 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

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →