🕵️ SicherheitslückenHak5: Hackers Just Poisoned the Rust Supply Chain | Threat Wire(01.09.2026 um 14:00 Uhr)
🕵️ SicherheitslückenHak5: Hackers Found a Way Into Humanoid Robots | Threat Wire(04.09.2026 um 15:04 Uhr)
🔧 AI Nachrichten Bits und so #1021 (Passwort für Laufwerk)(31.08.2026 um 22:15 Uhr)
🔧 AI Nachrichten Bits und so #1022 (Wie Weißbier)(06.09.2026 um 20:39 Uhr)
🍏 iOS / Mac OSHue-App 6.0 ist da: das sind die Neuerungen(07.09.2026 um 17:21 Uhr)
🕵️ SicherheitslückenHak5: Hackers Just Poisoned the Rust Supply Chain | Threat Wire(01.09.2026 um 14:00 Uhr)
🕵️ SicherheitslückenHak5: Hackers Found a Way Into Humanoid Robots | Threat Wire(04.09.2026 um 15:04 Uhr)
🔧 AI Nachrichten Bits und so #1021 (Passwort für Laufwerk)(31.08.2026 um 22:15 Uhr)
🔧 AI Nachrichten Bits und so #1022 (Wie Weißbier)(06.09.2026 um 20:39 Uhr)
🍏 iOS / Mac OSHue-App 6.0 ist da: das sind die Neuerungen(07.09.2026 um 17:21 Uhr)

🔧 Programmierung 🕛 kürzlich 5 Min Lesezeit
0

X Just Shipped an MCP Server. It Exposes 131 Tools With Zero Access Control.

↗ Quelle (dev.to)
🗣️ Stimme:
📑 Inhaltsübersicht

X (formerly Twitter) just released sits between your agent and the X MCP server, evaluating every tools/call against a YAML policy before it reaches the X API.



Here is a starter policy for the X MCP server:




CODE
version: "1"
description: "Policy for xdevplatform/xmcp"
default: "allow"
tools:
# === Block destructive tools entirely ===
deletePosts:
default: "deny"
deleteDirectMessagesEvents:
default: "deny"
deleteLists:
default: "deny"
deleteAllConnections:
default: "deny"
deleteCommunityNotes:
default: "deny"

# === Rate limit public-facing actions ===
createPosts:
rules:
- name: "post-rate-limit"
rate_limit: "5/hour"
on_deny: "Rate limit: max 5 posts per hour"

repostPost:
rules:
- name: "repost-rate-limit"
rate_limit: "10/hour"
on_deny: "Rate limit: max 10 reposts per hour"

likePost:
rules:
- name: "like-rate-limit"
rate_limit: "20/hour"
on_deny: "Rate limit: max 20 likes per hour"

# === Rate limit DMs and chat ===
createDirectMessagesByConversationId:
rules:
- name: "dm-rate-limit"
rate_limit: "10/hour"
on_deny: "Rate limit: max 10 DMs per hour"

createDirectMessagesByParticipantId:
rules:
- name: "dm-new-rate-limit"
rate_limit: "5/hour"
on_deny: "Rate limit: max 5 new DM conversations per hour"

sendChatMessage:
rules:
- name: "chat-rate-limit"
rate_limit: "10/hour"
on_deny: "Rate limit: max 10 chat messages per hour"

# === Rate limit social graph changes ===
followUser:
rules:
- name: "follow-rate-limit"
rate_limit: "10/hour"
on_deny: "Rate limit: max 10 follows per hour"

unfollowUser:
rules:
- name: "unfollow-rate-limit"
rate_limit: "10/hour"
on_deny: "Rate limit: max 10 unfollows per hour"

# === Global safety net ===
"*":
rules:
- name: "global-rate-limit"
rate_limit: "120/minute"
on_deny: "Global rate limit: max 120 tool calls per minute across all X tools"






This policy blocks all destructive tools outright, rate-limits public actions (posts, reposts, likes, DMs, follows), and applies a global cap to prevent runaway loops. Read operations pass through unrestricted.






Getting started






CODE
# Install Intercept
npm install -g @policylayer/intercept

# Run XMCP through Intercept with your policy
intercept -c x-policy.yaml -- python server.py






Save the YAML above as x-policy.yaml. Intercept proxies all MCP traffic through the policy engine — no changes to your agent or the XMCP server.



Adjust the limits to match your use case. A social media management agent might need higher post limits. A research agent that only reads trends and searches might not need write access at all — set default: "deny" and allowlist only the read tools.






The pattern is clear



Every major platform is shipping MCP servers. Stripe, GitHub, Slack, Cloudflare, and now X. None of them ship with access controls. The protocol does not require it, and the servers do not implement it.



X makes this pattern more visible because the consequences are public. A bad API call to Stripe affects your balance. A bad API call to X affects your reputation, in public, permanently.



The tools exist. The policies should too.



| Intercept on GitHub

Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
↗ Original-Artikel auf dev.to lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 0%
🟡 In Evaluierung 0%
🟢 Keine Auswirkung 0%
Spannende Innovation 0%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
1 Quelle
Hackers Just Poisoned the Rust Supply Chain | Threat Wire
1 Quelle
Hackers Found a Way Into Humanoid Robots | Threat Wire
1 Quelle
Bits und so #1021 (Passwort für Laufwerk)
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten X Just Shipped an MCP Server. It Exposes 131 Tools With Zero Access Control.

Thematisch verwandte Begriffe: Just, Shipped, Server, Exposes · 6 Treffer

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...