// SCAN REPORT

Satsignal

10 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 2 Jul 2026

1 can modify or destroy data

9 read-only

10 tools total

Community server · catalogue entry verified 02/07/2026

How to control Satsignal ↓

TOOL MAP

What Satsignal exposes to your agents

Read (9) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Satsignal tools

Write · Medium create_disclosure This is a Write operation because it creates new derived content (redacted disclosures) from existing data.

1 of Satsignal's 10 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Satsignal

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

Rate limit write operations

{
  "create_disclosure": {
    "limits": [
      {
        "counter": "create_disclosure_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "anchor_disclosable": {
    "limits": [
      {
        "counter": "anchor_disclosable_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 Satsignal — 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 SATSIGNAL →

Instant setup, no code required.

FULL CATALOGUE

All 10 Satsignal tools

WRITE 1 tools

Write create_disclosure Produce an audience-specific redacted disclosure from an

READ 9 tools

Read anchor_disclosable Anchor a payload as a SEALED, selectively-disclosable envelope Read anchor_file Anchor a local file: compute its sha256, POST to Read anchor_json Canonicalize a JSON object (sorted keys, compact Read anchor_text Anchor a UTF-8 text payload. Computes Read chain_confirm_bundle CHAIN-CONFIRM ONLY: open a local .mbnt bundle, extract Read lookup_hash Check whether a sha256 is anchored on-chain. Read-only, Read verify_bundle DEPRECATED + FAIL-CLOSED — this name silently produced Read verify_disclosure Verify a redacted disclosure .mbnt: confirm every REVEALED leaf Read verify_file_against_bundle FULL VERIFY: re-hash the original file, confirm it

FAQ

Questions about Satsignal

How do I prevent bulk modifications through Satsignal? +

The Satsignal server has 1 write tools including create_disclosure. 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 Satsignal.

How many tools does the Satsignal MCP server expose? +

10 tools across 2 categories: Read, Write. 9 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Satsignal? +

Register the Satsignal 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 Satsignal tool call.

Deterministic rules across all 10 Satsignal tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SATSIGNAL →

Instant setup, no code required.

10 Satsignal tools catalogued and risk-classified — across an index of 43,000+ MCP servers.