AI agents call twitter_notifications to retrieve information from Twitter Bridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves notification data from a logged-in Twitter/X session. It performs no modifications, deletions, or external actions—it only reads and returns information to the user. This is a straightforward Read category tool with minimal risk; the severity is low because accessing one's own notifications through an authenticated session has limited blast radius even if misused by an AI agent.
From the tool's definition Tool name 'twitter_notifications' and description 'Get your notifications' indicate a retrieval operation with no side effects. The verb 'Get' explicitly describes data querying.
Documented attack patterns abuse exactly the kind of access twitter_notifications gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twitter Bridge MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for twitter_notifications:
{
"version": "1",
"default": "deny",
"tools": {
"twitter_notifications": {}
}
}twitter_notifications is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get your notifications. It is categorised as a Read tool in the Twitter Bridge MCP MCP Server, which means it retrieves data without modifying state.
Register the Twitter Bridge 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 Bridge MCP. 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 Bridge MCP server (replica882/twitter-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Twitter Bridge MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Twitter Bridge MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.