integrations_capture_session

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

High RISK CLASS

Category Execute

Parameters 31 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-capture-session.md

WHAT IT DOES

What integrations_capture_session does on Dialogbrain

AI agents invoke integrations_capture_session to trigger actions in Dialogbrain. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`page_id`	string	Yes	page_id from a prior browser_open of the integration's site (logged in).
`base_url`	string	—	Or the integration's base URL, e.g. https://api.boomnow.com.
`integration_id`	integer	—	Integration id (from integrations.list).

Parameters from the server's own tool schema.

RISK

Why integrations_capture_session is rated High

This tool captures live authentication credentials (cookies including httpOnly, bearer tokens, API keys, custom auth headers) from an active browser session. It performs an active operation that harvests sensitive auth material from a live browser page.

From the tool's definition Restore an expired integration session by capturing the LIVE auth of an open browser page — captures the full storage_state (incl httpOnly cookies page JS can't read) into the bound identity; for token sessions it captures the auth headers

Risk signalsAccepts URL/endpoint input (base_url)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

integrations_capture_session Rate-limited

integrations_capture_session stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_capture_session": {
      "limits": [
        {
          "counter": "integrations_capture_session_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_capture_session call is checked against it from then on.

FAQ

Questions about integrations_capture_session

What does the integrations_capture_session tool do? +

Restore an expired integration session by capturing the LIVE auth of an open browser page — works for COOKIE sessions (browser_identity) AND TOKEN/HEADER sessions (bearer / api_key / custom_headers, e.g. Devise access-token/client/uid). First call browser_open(url, identity_name) for the integration's site (the page must be logged in AND have called its API), then pass that page_id here with integration_id or base_url. For cookie sessions it captures the full storage_state (incl httpOnly cookies page JS can't read) into the bound identity; for token sessions it captures the auth headers the page sends to the API host and binds them. Re-connects the integration. The captured secret never leaves the server (returns counts only). Generic — any site, any auth scheme, no local Playwright. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does integrations_capture_session accept? +

integrations_capture_session accepts 3 parameters: page_id, base_url, integration_id. Required: page_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on integrations_capture_session? +

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

integrations_capture_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit integrations_capture_session? +

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

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

integrations_capture_session 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 → High-risk tools on this server →

Across the catalogue

timed_capture on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →