Upload a media file and get back a media_id reusable in send_media_message. Multipart POST to /{phone_number_id}/media.
AI agents use upload_media to create or update resources in Mcp Afip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Afip environment.
The tool creates or stores data (a media file) and returns an identifier for subsequent use. This is a reversible write operation without permanent deletion or code execution. The severity is low because uploading media in a tax/invoicing context has limited blast radius — the files can be managed, replaced, or removed without financial impact or system compromise.
From the tool's definition Tool description states 'Upload a media file and get back a media_id' — this creates new media resources in the system via Multipart POST.
Documented attack patterns abuse exactly the kind of access upload_media gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Afip, and nothing reaches the server without passing your rules. This is the rule we recommend for upload_media:
{
"version": "1",
"default": "deny",
"tools": {
"upload_media": {
"limits": [
{
"counter": "upload_media_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
Upload a media file and get back a media_id reusable in send_media_message. Multipart POST to /{phone_number_id}/media. It is categorised as a Write tool in the Mcp Afip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for 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 Mcp Afip. Nothing to install.
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 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 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.
upload_media is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Afip, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Afip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.