Get recent @mentions of the authenticated account
AI agents call get_mentions to retrieve information from Twitter Read without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical mention data from the authenticated user's account without modifying, deleting, or executing any operations. It is a straightforward data query operation with no side effects, fitting the Read category. Low severity because misuse would only expose publicly-visible or user-accessible mention data without operational impact.
From the tool's definition Tool description states 'Get recent @mentions' with no write, delete, or execution capability indicated. Server description confirms this is for 'reading Twitter/X engagement data and metrics' with functions like 'get_replies, get_tweet_metrics,…
Attacks that exploit this kind of access
Get recent @mentions of the authenticated account. It is categorised as a Read tool in the Twitter Read MCP Server, which means it retrieves data without modifying state.
Register the Twitter Read MCP server in PolicyLayer and add a rule for get_mentions: 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 Read. Nothing to install.
get_mentions 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 get_mentions 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 get_mentions. 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.
get_mentions is provided by the Twitter Read MCP server (polsia-inc/twitter-read-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 →