xmtp-comms-guard

Enforce deterministic security controls for XMTP communications with validation and blocking.

23|5|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/EverClaw/EverClaw --skill xmtp-comms-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xmtp-comms-guard
Source: https://github.com/EverClaw/EverClaw/tree/main/skills/xmtp-comms-guard
Command: npx skills add https://github.com/EverClaw/EverClaw --skill xmtp-comms-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe XMTP communication by forcing every message through deterministic validation, peer authorization, replay protection, and trust-based policy checks. It replaces ad hoc messaging practices with a fail-closed security layer so agents can communicate without exposing sensitive data or bypassing governance.

Core Features & Use Cases

  • Guarded client enforcement: Routes all XMTP traffic through createGuardedXmtpClient instead of raw client usage.
  • Deterministic security pipeline: Checks message size, schema version, nonce replay, peer registry status, rate limits, PII exposure, prompt injection risk, and trust-context rules.
  • Audit and revocation workflows: Maintains hash-chain logs, supports peer revocation and key rotation, and surfaces approval flows for sensitive trust changes.
  • Use case: An EverClaw agent can safely exchange operational messages, reject malformed payloads, and block unauthorized or overly sensitive conversations before delivery.

Quick Start

Use this skill to wrap your XMTP client with guarded messaging so every conversation is validated, authenticated, and logged under deterministic security rules.

Frequently Asked Questions about xmtp-comms-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce security validation for XMTP messaging?

XMTP messaging security validation is enforced by routing all traffic through a guarded client that applies deterministic policy checks for schema, peer authorization, and replay protection. This ensures no unsafe messages bypass governance controls.

How do I prevent prompt injection attacks in agent messaging?

Prompt injection detection in agent messaging is handled by a deterministic security pipeline that scans payloads for injection risks before delivery. The system blocks unsafe traffic and fails closed when malicious content is identified.

Does XMTP communication support peer revocation and key rotation workflows?

XMTP communication supports peer revocation and key rotation through audit workflows that surface approval flows for sensitive trust changes. Hash-chain logging maintains an auditable record of all trust-context modifications.

What is the best way to block PII exposure in XMTP conversations?

Blocking PII exposure in XMTP conversations is best achieved by applying deterministic PII scanning rules within a fail-closed security layer. The guarded client intercepts and rejects messages containing sensitive data before they reach peers.

How do I implement nonce replay protection for XMTP messages?

Nonce replay protection for XMTP messages is implemented by validating nonce uniqueness within a deterministic security pipeline. The guarded client checks each message against replay rules and blocks any duplicate or unauthorized payloads.

Can I use a guarded XMTP client for audit-safe communication pipelines?

A guarded XMTP client can be used for audit-safe communication pipelines by enforcing hash-chain logging and deterministic trust-context rules. This wraps every conversation in fail-closed validation to ensure operational compliance.