AI agents call notifications_get 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 notifications from a Mastodon instance. No modification, deletion, or execution of external operations is indicated. The 'get' verb is a standard Read operation pattern. Even though the description is empty, the context (sibling tools like account_get, account_followers) and naming strongly indicate this is a simple data retrieval with no side effects.
From the tool's definition Tool name 'notifications_get' indicates a retrieval operation. The server description emphasizes 'read timelines' and 'search' as read operations.
Attacks that exploit this kind of access
notifications_get. 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 notifications_get: 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.
notifications_get 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 notifications_get 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 notifications_get. 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.
notifications_get 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 →