This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/giphy-trending.md
What giphy_trending does on UnClick
AI agents call giphy_trending 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 |
|---|---|---|---|
limit | number | — | GIFs to return (max 50, default 10) |
rating | string | — | Content rating cap |
api_key | string | Yes | Giphy API key |
Parameters from the server's own tool schema.
Why giphy_trending is rated Low
This tool queries and retrieves public trending GIF data from Giphy's API. It performs no data modification, deletion, code execution, or financial transactions. The operation is read-only and non-destructive. Severity is low as misuse would only affect the user experience with irrelevant GIF results, posing no security, privacy, or system risk.
From the tool's definition Tool name 'giphy_trending' and description 'Get trending GIFs from Giphy' indicate a retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs giphy_trending 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 giphy_trending, this is the rule to start with:
giphy_trending 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 giphy_trending call is checked against it from then on.
Questions about giphy_trending
Get trending GIFs from Giphy. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
giphy_trending accepts 3 parameters: limit, rating, api_key. Required: api_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 giphy_trending: 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.
giphy_trending 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 giphy_trending 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 giphy_trending. 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.
giphy_trending 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