unsplash_get_photo
Get a single Unsplash photo by id (URLs + attribution).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/unsplash-get-photo.md
What unsplash_get_photo does on UnClick
AI agents call unsplash_get_photo to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
photo_id | string | Yes | Unsplash photo id |
access_key | string | Yes | Unsplash Access Key |
Parameters from the server's own tool schema.
Why unsplash_get_photo is rated Low
This tool performs a data retrieval operation from Unsplash's public API. It fetches photo information by ID and returns URLs and attribution metadata. There are no side effects, no data modification, no execution of arbitrary code, and no destructive actions. This is a straightforward read operation with minimal risk—only low severity because even misuse would simply return publicly available image metadata.
From the tool's definition The tool 'Get a single Unsplash photo by id (URLs + attribution)' retrieves photo metadata and URLs from the Unsplash API. The verb 'Get' and the phrase 'URLs + attribution' indicate a read-only query operation that returns data without modification.
Attacks that exploit this kind of access
The rule that runs unsplash_get_photo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unsplash_get_photo, this is the rule to start with:
unsplash_get_photo is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every unsplash_get_photo call is checked against it from then on.
Questions about unsplash_get_photo
Get a single Unsplash photo by id (URLs + attribution). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
unsplash_get_photo accepts 2 parameters: photo_id, access_key. Required: photo_id, access_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for unsplash_get_photo: 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 UnClick. Nothing to install.
unsplash_get_photo is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the unsplash_get_photo 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_get_photo. 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_get_photo is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue