fidelitypass_verify_copy

Recompute a FidelityCopy/FidelityPass verdict from source and output bytes, or return N/A when no exact 1:1 copy is in scope. Missing bytes, stale metadata, or prose-only AI proof cannot PASS.

SERVERUnClick SOURCE@unclick/mcp-server

Low RISK CLASS

Category Read

Parameters 120 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/fidelitypass-verify-copy.md

WHAT IT DOES

What fidelitypass_verify_copy does on UnClick

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

Parameter	Type	Required	Description
`mode`	string	—	Verification mode. Defaults to raw_bytes or the provided receipt mode.
`receipt`	object	—	Optional previous FidelityCopy receipt to compare against recomputed hashes.
`copy_scope`	string	—	Explicit FidelityPass scope. Use not_applicable to record the XPass N/A row when no exact copy is in scope.
`output_ref`	string	—	Output pointer used in the recomputed receipt.
`proof_text`	string	—	Optional prose proof. Prose alone is suppressed, not accepted as PASS.
`source_ref`	string	—	Source pointer used in the recomputed receipt.
`output_text`	string	—	Exact output text to verify. Mutually exclusive with output_base64.
`source_text`	string	—	Exact source text to verify. Mutually exclusive with source_base64.
`scope_reason`	string	—	Reason why FidelityPass is N/A for this target. Used only when exact_copy_required=false or copy_scope=not_applicable.
`output_base64`	string	—	Exact output bytes as base64. Mutually exclusive with output_text.
`source_base64`	string	—	Exact source bytes as base64. Mutually exclusive with source_text.
`provenance_ref`	string	—	Optional Boardroom, issue, PR, or CopyRoom pointer for audit trail.

Parameters from the server's own tool schema.

RISK

Why fidelitypass_verify_copy is rated Low

This tool performs verification and comparison of data (checking if a copy matches source bytes), which is a read-only analytical operation. It returns a verdict or 'N/A' with no side effects mentioned. The output is informational, and no data is created, modified, or deleted.

From the tool's definition The tool description states it 'Recompute a FidelityCopy/FidelityPass verdict' and 'return N/A' — operations that retrieve and verify data without modifying it.

Risk signalsHigh parameter count (21 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fidelitypass_verify_copy safely

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

fidelitypass_verify_copy Allowed

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

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

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

FAQ

Questions about fidelitypass_verify_copy

What does the fidelitypass_verify_copy tool do? +

Recompute a FidelityCopy/FidelityPass verdict from source and output bytes, or return N/A when no exact 1:1 copy is in scope. Missing bytes, stale metadata, or prose-only AI proof cannot PASS. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does fidelitypass_verify_copy accept? +

fidelitypass_verify_copy accepts 12 parameters: mode, receipt, copy_scope, output_ref, proof_text, source_ref, output_text, source_text, scope_reason, output_base64, source_base64, provenance_ref. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fidelitypass_verify_copy? +

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

What risk level is fidelitypass_verify_copy? +

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

Can I rate-limit fidelitypass_verify_copy? +

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

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

fidelitypass_verify_copy is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

The MCP Attack Database →

Guides

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