unsplash_random_photo
Get a random Unsplash photo, optionally matching a query.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/unsplash-random-photo.md
What unsplash_random_photo does on UnClick
AI agents call unsplash_random_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 |
|---|---|---|---|
query | string | — | Optional topic to match |
access_key | string | Yes | Unsplash Access Key |
orientation | string | — | Filter by orientation |
Parameters from the server's own tool schema.
Why unsplash_random_photo is rated Low
This tool retrieves publicly available photo data from Unsplash without creating, modifying, deleting, or executing operations. It is a simple read-only query. The severity is low because there is no blast radius from misuse—returning a random or filtered photo cannot cause harm to systems, data, or finances.
From the tool's definition Tool description states 'Get a random Unsplash photo' — a retrieval operation with no modification, deletion, or execution of external code. The optional query parameter is used for filtering results, not executing arbitrary logic.
Attacks that exploit this kind of access
The rule that runs unsplash_random_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_random_photo, this is the rule to start with:
unsplash_random_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_random_photo call is checked against it from then on.
Questions about unsplash_random_photo
Get a random Unsplash photo, optionally matching a query. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
unsplash_random_photo accepts 3 parameters: query, access_key, orientation. Required: 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_random_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_random_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_random_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_random_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_random_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