Read your Twitter/X home feed. Requires auth cookies.
AI agents call twitter_feed to retrieve information from Twitter/X MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays feed data from a user's Twitter/X account without modifying, deleting, or executing operations on the platform. While it requires authentication cookies, the operation itself is purely retrieving data. The blast radius of misuse is low—an agent could see a user's feed but cannot post, delete, or perform financial transactions. This is a classic Read category tool.
From the tool's definition Tool name is 'twitter_feed' and description states 'Read your Twitter/X home feed.' The verb 'read' and the action of retrieving feed data indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
Read your Twitter/X home feed. Requires auth cookies. It is categorised as a Read tool in the Twitter/X MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Twitter/X MCP Server MCP server in PolicyLayer and add a rule for twitter_feed: 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/X MCP Server. Nothing to install.
twitter_feed 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_feed 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_feed. 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_feed is provided by the Twitter/X MCP Server MCP server (miles0sage/twitter-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 →