media.pexels.curated
Hand-picked high-quality curated photos from Pexels — updated daily. Returns photographer, multiple sizes, Pexels URL. Perfect for featured images and hero sections (Pexels)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/media.pexels.curated.md
What media.pexels.curated does on Apibase
AI agents call media.pexels.curated to retrieve information from Apibase 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 |
|---|---|---|---|
page | integer | — | Page number |
limit | integer | — | Number of curated photos (default 10, max 80) |
Parameters from the server's own tool schema.
Why media.pexels.curated is rated Low
Retrieves curated photo metadata from Pexels API; no side effects or data modification.
From the tool's definition Hand-picked high-quality curated photos from Pexels — updated daily. Returns photographer, multiple sizes, Pexels URL.
Attacks that exploit this kind of access
The rule that runs media.pexels.curated safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For media.pexels.curated, this is the rule to start with:
media.pexels.curated 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 Apibase, apply this rule, and every media.pexels.curated call is checked against it from then on.
Questions about media.pexels.curated
Hand-picked high-quality curated photos from Pexels — updated daily. Returns photographer, multiple sizes, Pexels URL. Perfect for featured images and hero sections (Pexels). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
media.pexels.curated accepts 2 parameters: page, limit. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for media.pexels.curated: 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 Apibase. Nothing to install.
media.pexels.curated 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 media.pexels.curated 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 media.pexels.curated. 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.
media.pexels.curated is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue