This record as markdown: /tools/io-github-alifanov-scopegate/twitter-follow-user.md
What twitter_follow_user does on ScopeGate
AI agents use twitter_follow_user to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why twitter_follow_user is rated Medium
Following a user on Twitter is a Write operation: it creates a new social relationship (follow) that is reversible by unfollowing. It does not delete data, execute code, or involve financial transactions. Misuse could cause reputational harm (e.g., an agent following unintended accounts at scale), hence medium severity.
From the tool's definition 'Follow a user' — creates a follow relationship on Twitter, which is a reversible social action (can be unfollowed).
Attacks that exploit this kind of access
The rule that runs twitter_follow_user 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_follow_user, this is the rule to start with:
twitter_follow_user stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_follow_user call is checked against it from then on.
Questions about twitter_follow_user
Follow a user. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate MCP server in PolicyLayer and add a rule for twitter_follow_user: 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_follow_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the twitter_follow_user 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_follow_user. 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_follow_user 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