AI agents call blog_get_trending to retrieve information from Blog Writer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention and position within the blog automation workflow strongly suggest this tool retrieves trending information for content ideation—a query/read operation with no side effects. While the empty description reduces confidence slightly, the pattern of similar 'blog_get_*' tools on this server (analytics, performance feedback) all appear to be read operations.
From the tool's definition Tool name 'blog_get_trending' suggests retrieving trending data/topics. The empty description is uninformative, but context from sibling tools (blog_generate_image, blog_get_analytics, blog_get_performance_feedback) indicates this server provides read-only…
Documented attack patterns abuse exactly the kind of access blog_get_trending gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Blog Writer, and nothing reaches the server without passing your rules. This is the rule we recommend for blog_get_trending:
{
"version": "1",
"default": "deny",
"tools": {
"blog_get_trending": {}
}
}blog_get_trending is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
blog_get_trending. It is categorised as a Read tool in the Blog Writer MCP Server, which means it retrieves data without modifying state.
Register the Blog Writer MCP server in PolicyLayer and add a rule for blog_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 Blog Writer. Nothing to install.
blog_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 blog_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 blog_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.
blog_get_trending is provided by the Blog Writer MCP server (sinmb79/blog-writer_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Blog Writer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Blog Writer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.