witness_export

Export chain for external audit

SERVERClaude Flow SOURCEclaude-flow

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What witness_export does on Claude Flow

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

RISK

Why witness_export is rated Medium

The tool exports data (Write category) rather than merely reading it—export implies transformation, serialization, or repackaging of data for external use. This is reversible and non-destructive. Severity is medium because exported audit data could be sensitive and misused if exported to untrusted parties, but the operation itself is not destructive or financial.

From the tool's definition Tool name 'witness_export' and description 'Export chain for external audit' indicate data extraction and serialization of audit chain records for external consumption.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

witness_export Rate-limited

witness_export 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": {
    "witness_export": {
      "limits": [
        {
          "counter": "witness_export_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 Claude Flow, apply this rule, and every witness_export call is checked against it from then on.

FAQ

Questions about witness_export

What does the witness_export tool do? +

Export chain for external audit. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on witness_export? +

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

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

Can I rate-limit witness_export? +

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

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

witness_export 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

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