witness_verify

Verify chain integrity

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/witness-verify.md

WHAT IT DOES

What witness_verify does on Claude Flow

AI agents call witness_verify to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why witness_verify is rated Low

Verification operations are typically read-only checks that validate correctness of some chain or sequence of data. No evidence of writes, deletions, or executions. Severity is medium because in an AI orchestration/hive-mind context, integrity verification over agent chains could expose sensitive structural or operational information.

From the tool's definition 'Verify chain integrity' — verification implies checking/querying a state without modifying it

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs witness_verify safely

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

witness_verify Allowed

witness_verify is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "witness_verify": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about witness_verify

What does the witness_verify tool do? +

Verify chain integrity. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on witness_verify? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for witness_verify: 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 Claude Flow. Nothing to install.

What risk level is witness_verify? +

witness_verify is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit witness_verify? +

Yes. Add a rate_limit block to the witness_verify 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 witness_verify completely? +

Set action: deny in the PolicyLayer policy for witness_verify. 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 witness_verify? +

witness_verify is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →