Agent Twitter Client

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

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

Last updated:

2 can modify or destroy data
12 read-only
14 tools total
Read (12) Write / Execute (2) Destructive / Financial (0)

Write operations (send_tweet, send_tweet_with_poll) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Rate limit write operations
send_tweet:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
follow_user:
  rules:
    - rate_limit: 60/minute

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

How do I prevent bulk modifications through Agent Twitter Client? +

The Agent Twitter Client server has 2 write tools including send_tweet, send_tweet_with_poll. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Agent Twitter Client MCP server expose? +

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

How do I add Intercept to my Agent Twitter Client setup? +

One line change. Instead of running the Agent Twitter Client server directly, prefix it with Intercept: intercept -c agent-twitter-client.yaml -- npx -y @agent-twitter-client-mcp. Download a pre-built policy from policylayer.com/policies/agent-twitter-client and adjust the limits to match your use case.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.