// SCAN REPORT

Twitter MCP Server

5 tools. 2 can modify or destroy data without limits.

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

Last updated: 4 Jul 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 04/07/2026

How to control Twitter MCP Server ↓

TOOL MAP

What Twitter MCP Server exposes to your agents

Read (3) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Twitter MCP Server tools

Write · Medium set_context_id This tool modifies session state reversibly (a context ID can be changed), making it a Write operation rather than Read. Write · High twitter_post Posting to Twitter is a Write operation that creates public content.

2 of Twitter MCP Server's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Twitter MCP Server

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

Rate limit write operations

{
  "set_context_id": {
    "limits": [
      {
        "counter": "set_context_id_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_context_id": {
    "limits": [
      {
        "counter": "get_context_id_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Create a free account and register Twitter MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TWITTER →

Instant setup, no code required.

FULL CATALOGUE

All 5 Twitter MCP Server tools

WRITE 2 tools

Write set_context_id Set the context ID for persistent sessions Write twitter_post Post a tweet to Twitter

READ 3 tools

Read get_context_id Get the current Browserbase context ID for persistent sessions Read print_extracted_data Prints the extracted data based on the provided schema. Read twitter_search Search for tweets on Twitter

FAQ

Questions about Twitter MCP Server

How do I prevent bulk modifications through Twitter MCP Server? +

The Twitter MCP Server server has 2 write tools including set_context_id, twitter_post. 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 Twitter MCP Server.

How many tools does the Twitter MCP Server MCP server expose? +

5 tools across 2 categories: Read, Write. 3 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Twitter MCP Server? +

Register the Twitter MCP Server 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 Twitter MCP Server tool call.

Deterministic rules across all 5 Twitter MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TWITTER →

Instant setup, no code required.

5 Twitter MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.