neuron_upload_media
Upload a media file (image, video, audio, or document) by providing its base64-encoded content. Returns a URL for use in messages and broadcasts.
This record as markdown: /tools/io-github-conquext-neuron/neuron-upload-media.md
What neuron_upload_media does on Neuron
AI agents use neuron_upload_media to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
base64 | string | Yes | Base64-encoded file content (without data URI prefix) |
filename | string | Yes | Original filename including extension (e.g., 'photo.jpg', 'report.pdf') |
mimetype | string | Yes | MIME type of the file (e.g., 'image/jpeg', 'image/png', 'application/pdf', 'video/mp4') |
Parameters from the server's own tool schema.
Why neuron_upload_media is rated Medium
This tool creates new media resources in the WhatsApp chatbot platform by accepting base64-encoded content and storing it. The output (generated URL) persists and can be used in downstream operations (messages, broadcasts), making it a reversible write operation.
From the tool's definition Tool description states 'Upload a media file' and 'Returns a URL for use in messages and broadcasts' - core write operation that creates new resources (media files) with persistent side effects (generated URLs).
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs neuron_upload_media safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_upload_media, this is the rule to start with:
neuron_upload_media 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 Neuron, apply this rule, and every neuron_upload_media call is checked against it from then on.
Questions about neuron_upload_media
Upload a media file (image, video, audio, or document) by providing its base64-encoded content. Returns a URL for use in messages and broadcasts. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_upload_media accepts 3 parameters: base64, filename, mimetype. Required: base64, filename, mimetype. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_upload_media: 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 Neuron. Nothing to install.
neuron_upload_media 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 neuron_upload_media 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 neuron_upload_media. 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.
neuron_upload_media is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
This server
Across the catalogue