twitter_get_user_mentions
Get tweets mentioning a user
This record as markdown: /tools/io-github-alifanov-scopegate/twitter-get-user-mentions.md
What twitter_get_user_mentions does on ScopeGate
AI agents call twitter_get_user_mentions to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why twitter_get_user_mentions is rated Low
This tool retrieves publicly available Twitter data (mentions of a user) without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with no side effects. The severity is low because the blast radius of misuse is minimal—an agent could retrieve mentions of any user, but this does not compromise security, finances, or data integrity.
From the tool's definition Tool is named 'twitter_get_user_mentions' and described as 'Get tweets mentioning a user'. The verb 'get' and 'mentioning' indicate data retrieval with no modification or execution.
Attacks that exploit this kind of access
The rule that runs twitter_get_user_mentions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For twitter_get_user_mentions, this is the rule to start with:
twitter_get_user_mentions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every twitter_get_user_mentions call is checked against it from then on.
Questions about twitter_get_user_mentions
Get tweets mentioning a user. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for twitter_get_user_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 ScopeGate. Nothing to install.
twitter_get_user_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 twitter_get_user_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 twitter_get_user_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.
twitter_get_user_mentions is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue