iot_witness_chain

Get witness chain provenance

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/iot-witness-chain.md

WHAT IT DOES

What iot_witness_chain does on Claude Flow

AI agents call iot_witness_chain 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 iot_witness_chain is rated Low

This tool retrieves historical provenance information from a witness chain (likely an immutable audit log or blockchain-style record). Reading provenance data is a non-destructive query operation that does not create, modify, delete, or execute external actions. It poses minimal risk as it only exposes information that already exists in the system.

From the tool's definition Tool name 'iot_witness_chain' with description 'Get witness chain provenance' indicates retrieval of existing provenance/audit chain data. The verb 'Get' explicitly signals a read operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs iot_witness_chain 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 iot_witness_chain, this is the rule to start with:

iot_witness_chain Allowed

iot_witness_chain 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": {
    "iot_witness_chain": {}
  }
}

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 iot_witness_chain call is checked against it from then on.

FAQ

Questions about iot_witness_chain

What does the iot_witness_chain tool do? +

Get witness chain provenance. 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 iot_witness_chain? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for iot_witness_chain: 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 iot_witness_chain? +

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

Can I rate-limit iot_witness_chain? +

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

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

iot_witness_chain 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 →