X MCP Adds Read-Only Mode for Safer Agents
X MCP now supports ?read_only=true, removing posting, DMs, bookmarks, blocks, and other write tools while rejecting write attempts even when tokens retain write scopes. The mode works across X API and Ads API MCP servers.
This is a practical safety boundary for agents connected to high-impact social accounts, though it complements rather than replaces least-privilege credentials and human approval.
- –Read-only mode makes research and monitoring safer by removing accidental side effects
- –URL-level capability control is easy to deploy across MCP clients
- –Server-side rejection matters because prompt instructions alone cannot reliably prevent writes
- –Developers still need a separate, carefully scoped configuration for legitimate posting or messaging workflows
DISCOVERED
21m ago
2026-11-10
PUBLISHED
1h ago
2026-11-10
RELEVANCE
AUTHOR
XDevelopers