artifacts_export_pdf
Snapshot an artifact's current version to a PDF saved in the workspace. NOTE: the PDF is a STATIC capture rendered with JavaScript disabled — interactive or JS-drawn content (charts on <canvas>, script-generated SVG) will not appear. Author charts as static SVG if they must show in the PDF. Retur...
This record as markdown: /tools/io-github-saloprj-dialogbrain/artifacts-export-pdf.md
What artifacts_export_pdf does on Dialogbrain
AI agents use artifacts_export_pdf 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 |
|---|---|---|---|
artifact_id | integer | Yes | The artifact to snapshot (its latest version). |
Parameters from the server's own tool schema.
Why artifacts_export_pdf is rated Medium
An AI agent can call artifacts_export_pdf 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.
Attacks that exploit this kind of access
The rule that runs artifacts_export_pdf 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 artifacts_export_pdf, this is the rule to start with:
artifacts_export_pdf 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every artifacts_export_pdf call is checked against it from then on.
Questions about artifacts_export_pdf
Snapshot an artifact's current version to a PDF saved in the workspace. NOTE: the PDF is a STATIC capture rendered with JavaScript disabled — interactive or JS-drawn content (charts on <canvas>, script-generated SVG) will not appear. Author charts as static SVG if they must show in the PDF. Returns the file_id; deliver it with messages.send(attachments=[file_id]). 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.
artifacts_export_pdf accepts 1 parameter: artifact_id. Required: artifact_id. 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 artifacts_export_pdf: 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.
artifacts_export_pdf is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the artifacts_export_pdf 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 artifacts_export_pdf. 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.
artifacts_export_pdf 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.
This server
Across the catalogue