AI agents call get_timeline to retrieve information from Twitter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries tweet data from a timeline. It is a straightforward read operation that fetches information without modifying state, executing code, or causing irreversible changes. The low severity reflects minimal risk: the worst-case misuse would be excessive API calls or unauthorized access to public tweets, which are non-destructive read operations.
From the tool's definition Tool name 'get_timeline' and description 'Get tweets from a user' indicate data retrieval with no side effects. It queries and returns existing tweets without modification, creation, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get_timeline gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twitter, and nothing reaches the server without passing your rules. This is the rule we recommend for get_timeline:
{
"version": "1",
"default": "deny",
"tools": {
"get_timeline": {}
}
}get_timeline 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 tweets from a user. It is categorised as a Read tool in the Twitter MCP Server, which means it retrieves data without modifying state.
Register the Twitter MCP server in PolicyLayer and add a rule for get_timeline: 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. Nothing to install.
get_timeline 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_timeline 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_timeline. 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_timeline is provided by the Twitter MCP server (twitter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Twitter, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Twitter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.