X

20 tools. 9 can modify or destroy data without limits.

9 write tools that can modify data. Rate limits recommended.

Last updated:

9 can modify or destroy data
11 read-only
20 tools total

Community server · catalogue entry checked 07/07/2026

How to control X ↓

What X exposes to your agents

Read (11) Write / Execute (9) Destructive / Financial (0)
High Risk

The most dangerous X tools

9 of X's 20 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control X

PolicyLayer is an MCP gateway — it sits between your AI agents and X, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations
{
  "add-delete-bookmark": {
    "limits": [
      {
        "counter": "add-delete-bookmark_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get-community": {
    "limits": [
      {
        "counter": "get-community_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register X — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON X →

Instant setup, no code required.

All 20 X tools

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about X

How do I prevent bulk modifications through X? +

The X server has 9 write tools including add-delete-bookmark, advanced-tweet, like-tweet. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach X.

How many tools does the X MCP server expose? +

20 tools across 3 categories: Destructive, Read, Write. 11 are read-only. 9 can modify, create, or delete data.

How do I enforce a policy on X? +

Register the X MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every X tool call.

Deterministic rules across all 20 X tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

20 X tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from X's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.