Track a photo download (required by Unsplash API guidelines when downloading photos). When you download a photo programmatically, you must call this tool to properly attribute the download to the photographer. This helps photographers understand how their work is being used. Args: - id (string): ...
AI agents use unsplash_track_download to create or update resources in Unsplash MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unsplash MCP Server environment.
This tool sends a download tracking event to the Unsplash API, which records/updates download statistics for a photo. It creates/modifies data on the server side (incrementing a counter or logging an event), making it a Write operation. It has no destructive, financial, or execution implications, and the blast radius of misuse is minimal — at worst it inflates download counts for a photographer.
From the tool's definition Track a photo download (required by Unsplash API guidelines when downloading photos)... This helps photographers understand how their work is being used.
Attacks that exploit this kind of access
Track a photo download (required by Unsplash API guidelines when downloading photos). When you download a photo programmatically, you must call this tool to properly attribute the download to the photographer. This helps photographers understand how their work is being used. Args: - id (string): Unsplash photo ID being downloaded Returns: Confirmation that download was tracked Examples: - Track download: id=. It is categorised as a Write tool in the Unsplash MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unsplash MCP Server MCP server in PolicyLayer and add a rule for unsplash_track_download: 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 Unsplash MCP Server. Nothing to install.
unsplash_track_download 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 unsplash_track_download 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 unsplash_track_download. 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.
unsplash_track_download is provided by the Unsplash MCP Server MCP server (mjordi/unsplash-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 →