Low Risk

retrieve_media_url

Resolve a media_id to a short-lived downloadable URL. The URL itself still requires the Bearer token to fetch.

How to control retrieve_media_url ↓

What retrieve_media_url does on Mcp Afip

AI agents call retrieve_media_url to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why retrieve_media_url needs a policy

This tool retrieves metadata (a URL) associated with a media identifier without side effects. It does not create, modify, delete, execute code, or transfer funds. The short-lived nature and token requirement further reduce risk. Classification as Read is appropriate.

From the tool's definition Tool description states 'Resolve a media_id to a short-lived downloadable URL' — this is a retrieval operation that queries/resolves data without modifying or deleting anything.

Documented attack patterns abuse exactly the kind of access retrieve_media_url gives an agent:

How to control retrieve_media_url

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 retrieve_media_url:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "retrieve_media_url": {}
  }
}

retrieve_media_url is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Afip — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about retrieve_media_url

What does the retrieve_media_url tool do? +

Resolve a media_id to a short-lived downloadable URL. The URL itself still requires the Bearer token to fetch. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on retrieve_media_url? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for retrieve_media_url: 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.

What risk level is retrieve_media_url? +

retrieve_media_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit retrieve_media_url? +

Yes. Add a rate_limit block to the retrieve_media_url 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.

How do I block retrieve_media_url completely? +

Set action: deny in the PolicyLayer policy for retrieve_media_url. 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.

What MCP server provides retrieve_media_url? +

retrieve_media_url 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.

Enforce policy on every Mcp Afip tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.