AI agents call twitter_search 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.
Searching tweets retrieves and queries publicly available or user-accessible data with no side effects, modifications, or state changes. This is a straightforward Read operation. Severity is low because search operations have minimal blast radius—the worst case is exposure of information the user can already access, with no ability to modify, delete, or affect other users or financial systems.
From the tool's definition Tool name 'twitter_search' and description 'Search tweets' indicate a query operation that retrieves data without modification.
Documented attack patterns abuse exactly the kind of access twitter_search 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_search:
{
"version": "1",
"default": "deny",
"tools": {
"twitter_search": {}
}
}twitter_search 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.
Search tweets. 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_search: 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_search 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_search 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_search. 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_search 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.