dual_provenance_create · DUAL MCP Server MCP: Risk & Policy

WHAT IT DOES

What dual_provenance_create does on DUAL MCP Server

AI agents use dual_provenance_create to create or update resources in DUAL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DUAL MCP Server environment.

WHY IT NEEDS A POLICY

Why dual_provenance_create needs a policy

The tool writes provenance data (creates records) with SHA-256 hashing, modifying the blockchain state by adding new entries. This is a Write operation rather than Read (passive query) or Destructive (irreversible deletion). While it exists in a Web3/blockchain context, the tool itself does not execute arbitrary code, move funds, or delete data.

From the tool's definition Tool name contains 'create' and description states 'Record the provenance of AI-generated content', indicating the tool creates or stores new provenance records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dual_provenance_create Rate-limited

dual_provenance_create 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": {
    "dual_provenance_create": {
      "limits": [
        {
          "counter": "dual_provenance_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DUAL MCP Server, so you can run agents against it safely.

FAQ

Questions about dual_provenance_create

What does the dual_provenance_create tool do? +

Record the provenance of AI-generated content with SHA-256 hashing. It is categorised as a Write tool in the DUAL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dual_provenance_create? +

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

What risk level is dual_provenance_create? +

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

Can I rate-limit dual_provenance_create? +

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

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

dual_provenance_create is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.