AI agents call status_reblogged_by 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 information about which accounts have reblogged a status. It performs a query ('Get') without creating, modifying, deleting, executing code, or committing financial transactions. The blast radius of misuse is minimal—an AI agent could only retrieve information that is typically public on Mastodon instances, with no capability to modify state or cause harm.
From the tool's definition Tool name 'status_reblogged_by' and description 'Get accounts that reblogged a status' indicate a retrieval operation that queries which accounts have reblogged a given status. This is a pure read operation with no side effects or modifications.
Attacks that exploit this kind of access
Get accounts that reblogged a status. 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 status_reblogged_by: 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.
status_reblogged_by 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 status_reblogged_by 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 status_reblogged_by. 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.
status_reblogged_by 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 →