AI agents call twitter_user to retrieve information from Twitter Bridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries user information without side effects. Even though it operates through browser automation, the action itself is non-destructive data retrieval. The blast radius of misuse is minimal—an attacker could enumerate user information but cannot modify data, execute arbitrary code, or cause financial harm through this tool alone.
From the tool's definition Tool name 'twitter_user' with description 'Get a user' indicates data retrieval. No modification, deletion, or execution of arbitrary operations. Retrieves publicly available user profile information via Twitter/X.
Documented attack patterns abuse exactly the kind of access twitter_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twitter Bridge MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for twitter_user:
{
"version": "1",
"default": "deny",
"tools": {
"twitter_user": {}
}
}twitter_user 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 a user. It is categorised as a Read tool in the Twitter Bridge MCP MCP Server, which means it retrieves data without modifying state.
Register the Twitter Bridge MCP server in PolicyLayer and add a rule for twitter_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 Twitter Bridge MCP. Nothing to install.
twitter_user 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_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_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_user is provided by the Twitter Bridge MCP server (replica882/twitter-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Twitter Bridge MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 Twitter Bridge MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.