Read your Twitter/X notifications and mentions. Requires auth cookies.
AI agents call twitter_notifications to retrieve information from Twitter/X MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays notification data to the user—a query operation with no side effects. It does not create, modify, delete, or execute actions. While it requires authentication cookies (which indicates it accesses account data), the operation itself is purely retrieving information already associated with the authenticated user's account.
From the tool's definition Tool name 'twitter_notifications' and description 'Read your Twitter/X notifications and mentions' explicitly indicate a read-only operation that retrieves data without modification.
Attacks that exploit this kind of access
Read your Twitter/X notifications and mentions. Requires auth cookies. It is categorised as a Read tool in the Twitter/X MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Twitter/X MCP Server MCP server in PolicyLayer and add a rule for twitter_notifications: 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 Twitter/X MCP Server. Nothing to install.
twitter_notifications 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 twitter_notifications 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 twitter_notifications. 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.
twitter_notifications is provided by the Twitter/X MCP Server MCP server (miles0sage/twitter-mcp). 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 →