crm_media_upload
Upload a file to the CRM media library. Provide a hosted URL or file data. Max 25MB.
This record as markdown: /tools/io-github-0nork-0nmcp/crm-media-upload.md
What crm_media_upload does on 0nmcp
AI agents use crm_media_upload to create or update resources in 0nmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0nmcp environment.
Why crm_media_upload is rated Medium
The tool creates or modifies data by uploading files to a CRM system's media library. It is reversible (files can typically be deleted), so it does not qualify as Destructive.
From the tool's definition Tool name contains 'upload' and description states 'Upload a file to the CRM media library.' This creates new data in the system that persists.
Attacks that exploit this kind of access
The rule that runs crm_media_upload safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crm_media_upload, this is the rule to start with:
crm_media_upload 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 0nmcp, apply this rule, and every crm_media_upload call is checked against it from then on.
Questions about crm_media_upload
Upload a file to the CRM media library. Provide a hosted URL or file data. Max 25MB. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 0n MCP server in PolicyLayer and add a rule for crm_media_upload: 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 0nmcp. Nothing to install.
crm_media_upload 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 crm_media_upload 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 crm_media_upload. 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.
crm_media_upload is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue