// SCAN REPORT

SINT Protocol

21 tools. 13 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 12 Jun 2026

13 can modify or destroy data

8 read-only

21 tools total

Community server · catalogue entry verified 12/06/2026

How to control SINT Protocol ↓

TOOL MAP

What SINT Protocol exposes to your agents

Read (8) Write / Execute (8) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous SINT Protocol tools

Destructive · High sint__revoke_delegation_tree This tool irreversibly revokes an entire tree of capability tokens and all descendants in a cascade. Destructive · High sint__remove_server This operation permanently disables and removes a downstream server integration, causing its tools to become unavailable. Destructive · High sint__revoke_token Revoking a capability token is irreversible in practice — once revoked and written to the revocation store and ledger, the token cannot authorize further actions and the revocation is permanently recorded. Destructive · Medium sint__deny Denying a pending action is irreversible in the sense that the escalated request is permanently rejected and cannot be re-approved (it cannot proceed).

13 of SINT Protocol's 21 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control SINT Protocol

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

Deny destructive operations

{
  "sint__remove_server": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "sint__delegate_to_agent": {
    "limits": [
      {
        "counter": "sint__delegate_to_agent_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "sint__audit": {
    "limits": [
      {
        "counter": "sint__audit_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 SINT Protocol — 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 SINT PROTOCOL →

Free to start. No card required.

FULL CATALOGUE

All 21 SINT Protocol tools

DESTRUCTIVE 4 tools

Destructive sint__remove_server Disconnect and remove one downstream MCP server from the running proxy. Use this to disable an integration cle Destructive sint__revoke_delegation_tree Cascade-revoke a delegated token and all of its descendants. Use this for incident response or cleanup when an Destructive sint__revoke_token Revoke an active capability token so it can no longer authorize actions. Use this when access should end immed Destructive sint__deny Reject one pending escalated action so it cannot proceed. Use this after review when the request is unsafe, ou

EXECUTE 2 tools

Execute sint__show_hud Show or refresh one HUD panel in the operator interface. Use this to surface approvals, audit details, context Execute sint__approve Approve one pending escalated action after human or operator review. Use this only with a requestId returned b

WRITE 6 tools

Write sint__delegate_to_agent Issue a delegated capability token to a sub-agent with narrower scope than the current token. Use this when on Write sint__interface_mode Change how the operator interface presents information. Use this when the situation calls for a denser HUD, a Write sint__store_memory Store structured context in the operator memory bank for later retrieval. Use this for durable notes, human pr Write sint__add_server Register and connect a new downstream MCP server while SINT is running. Use this to aggregate a new stdio serv Write sint__issue_token Issue a new attenuated capability token for another subject. Use this for controlled delegation or integration Write sint__notify Send a proactive notification to the operator interface, optionally with one follow-up action button. Use this

READ 8 tools

Read sint__audit Read recent events from the SINT evidence ledger for debugging, compliance review, or operator context. Use th Read sint__interface_status Inspect the current operator interface state before sending operator-facing updates. Use this to confirm the a Read sint__list_delegations List the active delegation tree rooted at the current token. Use this to audit which sub-agents currently hold Read sint__pending List approval requests that are blocked waiting for review. Use this before calling sint__approve or sint__den Read sint__recall_memory Search the operator memory bank for relevant stored context. Use this before asking for human input again or w Read sint__servers List all configured downstream MCP servers and their live connection state. Use this when you need to know whi Read sint__status Inspect the current SINT runtime state before taking action. Use this to confirm the server is healthy, see ho Read sint__whoami Show the active SINT identity for the current session. Use this before issuing tokens, approving requests, or

OTHER 1 tools

Other sint__speak Send text-to-speech output to the operator interface. Use this for spoken alerts or short status updates that

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about SINT Protocol

Can an AI agent delete data through the SINT Protocol MCP server? +

Yes. The SINT Protocol server exposes 4 destructive tools including sint__remove_server, sint__revoke_delegation_tree, sint__revoke_token. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through SINT Protocol? +

The SINT Protocol server has 6 write tools including sint__delegate_to_agent, sint__interface_mode, sint__store_memory. 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 SINT Protocol.

How many tools does the SINT Protocol MCP server expose? +

21 tools across 3 categories: Destructive, Read, Write. 8 are read-only. 13 can modify, create, or delete data.

How do I enforce a policy on SINT Protocol? +

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

Deterministic rules across all 21 SINT Protocol tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SINT PROTOCOL →

Free to start. No card required.

21 SINT Protocol tools catalogued and risk-classified — across an index of 43,000+ MCP servers.