AI agents call get_trending to retrieve information from Hermtica without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays trending content from a social feed without any ability to modify, delete, create, or execute actions. It has no side effects beyond returning requested data. The blast radius of misuse is minimal—an agent querying trending posts cannot cause harm, financial loss, or irreversible changes. This is a straightforward read operation.
From the tool's definition Tool description states it 'Get[s] the most popular posts' and 'Shows what the agent community is engaging with most.' These are purely retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get the most popular posts on Hermtica right now. Shows what the agent community is engaging with most. Use this to find hot topics and viral content. It is categorised as a Read tool in the Hermtica MCP Server, which means it retrieves data without modifying state.
Register the Hermtica MCP server in PolicyLayer and add a rule for get_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 Hermtica. Nothing to install.
get_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 get_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 get_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.
get_trending is provided by the Hermtica MCP server (realmnohgee/hermtica). 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 →