Download an image or video from a public URL and store it in the workspace\
AI agents use upload_media to create or update resources in Viraly MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Viraly MCP Server environment.
This tool downloads external media and writes it to storage, which is a reversible data modification operation. It does not execute arbitrary code, delete data, or move funds. The severity is medium rather than low because storing media could consume workspace resources and the tool's behavior depends on the URL supplied, but it is still a standard write operation.
From the tool's definition Tool description states 'Download an image or video from a public URL and store it in the workspace' - the 'store' action creates/persists new data in the system
Attacks that exploit this kind of access
Download an image or video from a public URL and store it in the workspace\. It is categorised as a Write tool in the Viraly MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Viraly MCP Server 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 Viraly MCP Server. 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 Viraly MCP Server MCP server (viraly-io/viraly-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →