Search for users by query (paginated).
AI agents call search_user to retrieve information from Twikit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves user information based on search criteria. It performs a read-only operation that does not create, modify, delete, or execute any actions. The pagination indicates standard search result retrieval. No data is altered, no code is executed, and no external operations are triggered by this tool.
From the tool's definition Tool name 'search_user' and description 'Search for users by query (paginated)' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access search_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Twikit, and nothing reaches the server without passing your rules. This is the rule we recommend for search_user:
{
"version": "1",
"default": "deny",
"tools": {
"search_user": {}
}
}search_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.
Search for users by query (paginated). It is categorised as a Read tool in the Twikit MCP Server, which means it retrieves data without modifying state.
Register the Twikit MCP server in PolicyLayer and add a rule for search_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 Twikit. Nothing to install.
search_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 search_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 search_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.
search_user is provided by the Twikit MCP server (tangivis/twitter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Twikit, 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.
59 Twikit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.