AI agents call trending_statuses to retrieve information from Mastodon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves public trending status information from the Mastodon instance without creating, modifying, deleting, or executing any changes. It is a simple data query operation analogous to searching or listing, which falls squarely into the Read category. Severity is low because misuse would only expose public information that is already visible to other users.
From the tool's definition Tool name 'trending_statuses' and description 'Get trending statuses on the instance' indicate a retrieval operation with no side effects. The verb 'Get' and the passive nature of querying public trending data confirm this is a read-only action.
Attacks that exploit this kind of access
Get trending statuses on the instance. It is categorised as a Read tool in the Mastodon MCP Server, which means it retrieves data without modifying state.
Register the Mastodon MCP server in PolicyLayer and add a rule for trending_statuses: 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 Mastodon. Nothing to install.
trending_statuses 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 trending_statuses 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 trending_statuses. 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.
trending_statuses is provided by the Mastodon MCP server (vitexsoftware/mastodon-mcp-server). 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 →