integrations_set_auth

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

Medium RISK CLASS

Category Write

Parameters 50 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-set-auth.md

WHAT IT DOES

What integrations_set_auth does on Dialogbrain

AI agents use integrations_set_auth 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 to set: {type, token?, header_name?, headers?(object), identity_id?, identity_name?, extract?(object)}. Omit to only refresh cookies on an existing browser
`cookies`	array	—	Cookies to merge into the bound browser identity. Each {name, value, domain?, path?, expires?}. Existing names are overwritten; new ones added.
`base_url`	string	—	Or the integration's base URL, e.g. https://api.boomnow.com.
`local_storage`	array	—	localStorage entries to merge. Each {origin, name, value}.
`integration_id`	integer	—	Integration id (from integrations.list).

Parameters from the server's own tool schema.

RISK

Why integrations_set_auth is rated Medium

This tool creates or modifies authentication credentials and configuration for HTTP-API integrations. While it doesn't directly read/execute/delete data, updating auth credentials is a Write operation that changes system state reversibly.

From the tool's definition Tool description states 'Set or update the authentication on an HTTP-API integration' and accepts parameters like bearer tokens, API keys, custom headers, and browser identity credentials. The tool modifies authentication configuration for integrations.

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_set_auth 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_set_auth, this is the rule to start with:

integrations_set_auth Rate-limited

integrations_set_auth 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_set_auth": {
      "limits": [
        {
          "counter": "integrations_set_auth_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_set_auth call is checked against it from then on.

FAQ

Questions about integrations_set_auth

What does the integrations_set_auth tool do? +

Set or update the authentication on an HTTP-API integration, generically. Identify it by integration_id or base_url. Pass auth = {type: bearer|api_key|basic|custom_headers|browser_identity|none, ...}: bearer/basic → {token}; api_key → {token, header_name?}; custom_headers → {headers:{name:value,...}}; browser_identity → {identity_id|identity_name, extract}. Token values are encrypted; nothing is stored in cleartext. To only refresh a browser_identity session, OMIT auth and pass cookies (and/or local_storage) — they are merged into the bound identity without touching its config. (oauth2 / service_account use the REST settings flow.). 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_set_auth accept? +

integrations_set_auth accepts 5 parameters: auth, cookies, base_url, local_storage, integration_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on integrations_set_auth? +

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

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

Can I rate-limit integrations_set_auth? +

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

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

integrations_set_auth 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

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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