files_get_base64
Download one or more files server-side and return their content as base64-encoded strings. Use this to inspect images, PDFs, or any binary file attached to messages when you cannot access presigned S3 URLs directly. Supports up to 5 files per call, max 15 MB each. For large files batch in groups ...
This record as markdown: /tools/io-github-saloprj-dialogbrain/files-get-base64.md
What files_get_base64 does on Dialogbrain
AI agents call files_get_base64 to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_ids | array | Yes | List of file IDs to fetch as base64 (max 5). Get IDs from files.info or message attachment_file_ids. |
Parameters from the server's own tool schema.
Why files_get_base64 is rated Low
This tool retrieves and reads file content without creating, modifying, or deleting data. It is clearly a Read operation. Severity is medium rather than low because: (1) files may contain sensitive information (PII, credentials, proprietary data) accessible through message attachments in a unified inbox spanning WhatsApp, Telegram, and Email; (2) base64 decoding enables an agent to inspect arbitrary binary content…
From the tool's definition Tool description states it will 'Download one or more files server-side and return their content as base64-encoded strings' with explicit purpose to 'inspect images, PDFs, or any binary file attached to messages'.
Attacks that exploit this kind of access
The rule that runs files_get_base64 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 files_get_base64, this is the rule to start with:
files_get_base64 is read-only, so it stays allowed. 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 files_get_base64 call is checked against it from then on.
Questions about files_get_base64
Download one or more files server-side and return their content as base64-encoded strings. Use this to inspect images, PDFs, or any binary file attached to messages when you cannot access presigned S3 URLs directly. Supports up to 5 files per call, max 15 MB each. For large files batch in groups of 1-2 to avoid oversized responses. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
files_get_base64 accepts 1 parameter: file_ids. Required: file_ids. 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 files_get_base64: 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.
files_get_base64 is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the files_get_base64 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 files_get_base64. 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.
files_get_base64 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