Get trending models from Hugging Face.
AI agents call get_trending_models to retrieve information from Hf Trending without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries trending model information from Hugging Face without modifying, executing, or deleting any data. It is purely informational with no capability to change state or trigger external operations. The blast radius of misuse is minimal—worst case, an AI agent could retrieve trending model metadata repeatedly, which has negligible security impact.
From the tool's definition Tool name 'get_trending_models' and description 'Get trending models from Hugging Face' indicate data retrieval. The sibling tools 'get_trending_datasets', 'get_trending_spaces', and 'search_trending' are all query/retrieval operations with no side effects.
Attacks that exploit this kind of access
Get trending models from Hugging Face. It is categorised as a Read tool in the Hf Trending MCP Server, which means it retrieves data without modifying state.
Register the Hf Trending MCP server in PolicyLayer and add a rule for get_trending_models: 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 Hf Trending. Nothing to install.
get_trending_models 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 get_trending_models 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 get_trending_models. 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.
get_trending_models is provided by the Hf Trending MCP server (kukapay/hf-trending-mcp). 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 →