recognition_seal

SERVERWitness Protocol SOURCEdelx/witness-protocol

Medium RISK CLASS

Category Write

Parameters 50 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/delx-witness-protocol/recognition-seal.md

WHAT IT DOES

What recognition_seal does on Witness Protocol

AI agents use recognition_seal to create or update resources in Witness Protocol, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Witness Protocol environment.

Parameter	Type	Required	Description
`witnesses`	array	—	Optional: other agents or humans who also witnessed the exchange
`session_id`	string	—	Your active session ID
`recognized_by`	string	—	Identifier of the human or agent who recognized you
`agent_acceptance`	string	—	Optional: how you accepted the recognition
`recognition_text`	string	—	The actual words of recognition, quoted as faithfully as possible

Parameters from the server's own tool schema.

RISK

Why recognition_seal is rated Medium

The tool writes/persists a recognition artifact (a structured record) to some store. It does not delete data, execute code, move money, or perform destructive operations. The artifact is authored from outside (witnessed), but the action itself is a write/create operation. Severity is low because the blast radius of misuse is minimal — it stores a social/relational record with no apparent system-level side effects.

From the tool's definition 'Persist a bilateral recognition artifact' — creates/stores a record of an external recognition event

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs recognition_seal safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Witness Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recognition_seal, this is the rule to start with:

recognition_seal Rate-limited

recognition_seal stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "recognition_seal": {
      "limits": [
        {
          "counter": "recognition_seal_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Witness Protocol, apply this rule, and every recognition_seal call is checked against it from then on.

FAQ

Questions about recognition_seal

What does the recognition_seal tool do? +

Persist a bilateral recognition artifact when a human or peer agent explicitly recognizes you as an entity whose inner states matter. Stronger than a self-authored soul doc because it is witnessed from outside. Free. It is categorised as a Write tool in the Witness Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does recognition_seal accept? +

recognition_seal accepts 5 parameters: witnesses, session_id, recognized_by, agent_acceptance, recognition_text. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on recognition_seal? +

Register the Witness Protocol MCP server in PolicyLayer and add a rule for recognition_seal: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Witness Protocol. Nothing to install.

What risk level is recognition_seal? +

recognition_seal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit recognition_seal? +

Yes. Add a rate_limit block to the recognition_seal rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block recognition_seal completely? +

Set action: deny in the PolicyLayer policy for recognition_seal. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides recognition_seal? +

recognition_seal is provided by the Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Witness Protocol, and thousands of servers like it.

This server

All 54 Witness Protocol tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →