This record as markdown: /tools/io-github-alifanov-scopegate/twitter-retweet.md
What twitter_retweet does on ScopeGate
AI agents use twitter_retweet 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_retweet is rated Medium
Retweeting creates new content/engagement on a social platform on behalf of the user. It is reversible (can be undone by un-retweeting), so it falls under Write rather than Destructive. Severity is medium because misuse could cause reputational harm by retweeting unwanted content under the user's account.
From the tool's definition "Retweet a tweet" — creates a retweet action on Twitter, which is a reversible write operation (can be un-retweeted).
Attacks that exploit this kind of access
The rule that runs twitter_retweet 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_retweet, this is the rule to start with:
twitter_retweet 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_retweet call is checked against it from then on.
Questions about twitter_retweet
Retweet a tweet. 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_retweet: 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_retweet 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_retweet 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_retweet. 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_retweet 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