fidelitycopy_copy
Create a deterministic FidelityCopy receipt for exact copy work. AI may request the copy, but this tool computes source/output hashes and returns PASS only when the selected mode proves exact or approved fidelity.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/fidelitycopy-copy.md
What fidelitycopy_copy does on UnClick
AI agents use fidelitycopy_copy to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | Verification mode. Defaults to raw_bytes. |
output_ref | string | — | Output pointer used in the receipt. |
source_ref | string | — | Source pointer used in the receipt. |
output_text | string | — | Output text for approved_transform mode. |
source_text | string | — | Exact source text to copy. Mutually exclusive with source_base64. |
output_base64 | string | — | Output bytes for approved_transform mode as base64. |
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. |
allowed_changes | object | — | Required for approved_transform PASS. |
destination_label | string | — | Human label for the output destination when output_ref is not supplied. |
copyroom_source_packet | object | — | CopyRoom source packet used as the source of truth. Mutually exclusive with source_text/source_base64. |
Parameters from the server's own tool schema.
Why fidelitycopy_copy is rated Medium
The tool creates a new artifact (a receipt) and performs copy verification. It does not merely read/query existing data — it produces a new document/record (the receipt). It does not execute arbitrary code, delete data, or move money. The primary action is generating/writing a fidelity receipt, making Write the most appropriate category.
From the tool's definition 'Create a deterministic FidelityCopy receipt for exact copy work' — the tool creates a receipt/record and computes hashes to verify copy fidelity, producing a PASS/FAIL result
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs fidelitycopy_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 fidelitycopy_copy, this is the rule to start with:
fidelitycopy_copy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every fidelitycopy_copy call is checked against it from then on.
Questions about fidelitycopy_copy
Create a deterministic FidelityCopy receipt for exact copy work. AI may request the copy, but this tool computes source/output hashes and returns PASS only when the selected mode proves exact or approved fidelity. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
fidelitycopy_copy accepts 11 parameters: mode, output_ref, source_ref, output_text, source_text, output_base64, source_base64, provenance_ref, allowed_changes, destination_label, copyroom_source_packet. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for fidelitycopy_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.
fidelitycopy_copy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fidelitycopy_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.
Set action: deny in the PolicyLayer policy for fidelitycopy_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.
fidelitycopy_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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue