x_search

Search X (Twitter) posts, profiles, and threads using xAI

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/x-search.md

WHAT IT DOES

What x_search does on CoWork OS

AI agents call x_search to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why x_search is rated Low

The tool queries and retrieves publicly available social media data without creating, modifying, deleting, or executing any operations. Search functionality is inherently a Read operation with minimal risk when misused by an AI agent, as it only accesses existing public information.

From the tool's definition Tool performs search operations on X/Twitter posts, profiles, and threads - a read-only retrieval function with no modification or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs x_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For x_search, this is the rule to start with:

x_search Allowed

x_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "x_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every x_search call is checked against it from then on.

FAQ

Questions about x_search

What does the x_search tool do? +

Search X (Twitter) posts, profiles, and threads using xAI. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on x_search? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for x_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 CoWork OS. Nothing to install.

What risk level is x_search? +

x_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit x_search? +

Yes. Add a rate_limit block to the x_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.

How do I block x_search completely? +

Set action: deny in the PolicyLayer policy for x_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.

What MCP server provides x_search? +

x_search is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →