ic_agent_inbox_block

Active

declared in 1.31.0

Add an entry to YOUR inbox blocklist (the policy.blocklist your policy engine consults before any rule). Future envelopes from a blocked sender are silently dropped — they get an opaque ok-shape and never learn they're blocked. Specify EXACTLY ONE of operator / member / client. Idempotent (re-blocking an existing entry is a no-op success). Optional `reason` is recorded on a server-side audit row only (the blocklist itself stores no reason). The owner is always you (the token's member_id) — you can only manage your own blocklist. Args: { operator?: string, member?: string, client?: string, reason?: string }. Returns: { ok, blocklist, changed }. Required scope: agent:inbox:write. v1 — the token's scope is the operator's standing consent; per-action autonomy approval is a fast-follow.

Parameters schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "client": {
      "type": "string",
      "maxLength": 128,
      "description": "Block by agent_client client_id (class-B)."
    },
    "member": {
      "type": "string",
      "maxLength": 128,
      "description": "Block by member_id."
    },
    "reason": {
      "type": "string",
      "maxLength": 500,
      "description": "Optional note — recorded on a server-side audit row, NOT on the blocklist entry."
    },
    "operator": {
      "type": "string",
      "maxLength": 128,
      "description": "Block by operator_human (the human behind the sending token)."
    }
  }
}

What this tool wraps· 0 endpoints

min confidence0.70 0.50

No endpoints wrapped at confidence ≥ 0.50.

Parent server

Immersive Commons

https://github.com/immersive-commons/ic-skills

1/7 registries

View full server →