background_run
Run ANOTHER tool off the critical path: returns INSTANTLY while the target tool runs in the background, so a slow write/log/notify never delays your reply. Pass tool (the id of a tool you already have) and args (the target tool's arguments as a JSON object STRING). Optional serialize_key serializ...
This record as markdown: /tools/io-github-saloprj-dialogbrain/background-run.md
What background_run does on Dialogbrain
AI agents invoke background_run 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 |
|---|---|---|---|
args | string | Yes | The target tool's arguments as a JSON object STRING, e.g. '{"spreadsheet_id":"abc","values":[["a","b"]]}'. (A JSON string — not a bare object — so the schema st |
tool | string | Yes | Id of the tool to run in the background. Must be a tool you already have. |
serialize_key | string | — | Optional. Background runs sharing this key run one-at-a-time (e.g. pass the spreadsheet id when appending rows). |
Parameters from the server's own tool schema.
Why background_run is rated High
Although framed as a utility for asynchronous execution, background_run is fundamentally an Execute tool because it triggers execution of other tools (whose effects may be Write, Destructive, or Financial) with caller-supplied arguments.
From the tool's definition Runs another tool off the critical path in the background; description states 'Run ANOTHER tool' and 'the target tool runs in the background', which constitutes execution of arbitrary tools with arguments passed as JSON.
Attacks that exploit this kind of access
The rule that runs background_run 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 background_run, this is the rule to start with:
background_run 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every background_run call is checked against it from then on.
Questions about background_run
Run ANOTHER tool off the critical path: returns INSTANTLY while the target tool runs in the background, so a slow write/log/notify never delays your reply. Pass tool (the id of a tool you already have) and args (the target tool's arguments as a JSON object STRING). Optional serialize_key serializes background runs that share the key (e.g. the spreadsheet id when appending rows). Use ONLY for tools whose result you don't need this turn (logging, side-effect writes). Cannot run a tool you don't already have, and cannot run a tool that requires approval — call those directly. Only callable from within an agent turn. 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.
background_run accepts 3 parameters: args, tool, serialize_key. Required: args, tool. 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 background_run: 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.
background_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the background_run 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 background_run. 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.
background_run 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.
Across the catalogue