AI agents call status_context 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 thread context by fetching ancestor and descendant statuses. It is a query/fetch operation with no side effects, no data modification, no code execution, and no destructive or financial implications. It falls squarely into the Read category with low severity due to minimal blast radius if misused.
From the tool's definition Tool name 'status_context' and description 'Get ancestors and descendants of a status (thread context)' indicate a read-only retrieval operation that fetches related statuses without modifying any data.
Attacks that exploit this kind of access
Get ancestors and descendants of a status (thread context). 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_context: 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_context 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_context 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_context. 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_context 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 →