Upload a local media file to Google Photos. Reads bytes from filePath and creates a new media item.
AI agents use upload_media to create or update resources in Google Photos MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Photos MCP Server environment.
Upload creates new media items in Google Photos, which is a reversible Write operation. It does not execute arbitrary code, delete data, or involve financial transactions. Severity is medium because an agent could add unwanted, sensitive, or numerous files to a user's library, but the harm is mitigated by the fact that uploads can be deleted and do not expose existing data or execute code.
From the tool's definition Tool description explicitly states 'Upload a local media file to Google Photos' and 'creates a new media item' — these are Write operations that modify the user's Google Photos library by adding new data reversibly.
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 Google Photos MCP Server, 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 local media file to Google Photos. Reads bytes from filePath and creates a new media item. It is categorised as a Write tool in the Google Photos MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Photos 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 Google Photos 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 Google Photos MCP Server MCP server (savethepolarbears/google-photos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Photos MCP Server, 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.
19 Google Photos MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.