# reproduce

Un-flatten a flat design image into editable layers and reproduce it bit-perfect, returning the fidelity score. Returns: A JSON string with a bit_perfect flag and fidelity metrics (mae, psnr, exact-match %, stray px).

Agent View of the PolicyLayer registry record for `reproduce`. HTML page: https://policylayer.com/tools/design-reprise-reprise/reproduce

## Facts

- Tool: `reproduce`
- Server: Reprise (`https://tepesama-reprise-mcp.hf.space/gradio_api/mcp/http`) — https://policylayer.com/tools/design-reprise-reprise.md
- Homepage: https://github.com/https://tepesama-reprise-mcp.hf.space/gradio_api/mcp/http
- Risk category: Execute (High risk)
- Registry record: grade B, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `image` | string | no | The source design image as an http(s) URL or a base64 data URL. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "reproduce",
    "arguments": {}
  }
}
```

## Why reproduce is rated High

The tool performs a non-trivial computational operation (image analysis, layer decomposition, and reproduction) that goes beyond simple data retrieval or storage write. It executes an image processing pipeline and returns derived metrics. It does not irreversibly delete data, move money, or merely read existing records — it actively transforms and reproduces an artifact, classifying it as Execute.

From the tool's own definition: "'Un-flatten a flat design image into editable layers and reproduce it bit-perfect' — triggers an external operation (image processing/layer decomposition) and returns computed fidelity metrics; 'reproduce it bit-perfect' implies running a generation/rendering…"

## Use case

AI agents invoke reproduce to trigger actions in Reprise. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Reprise:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reproduce": {
      "limits": [
        {
          "counter": "reproduce_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Reprise (2)

- `autodetect` — Read — https://policylayer.com/tools/design-reprise-reprise/autodetect.md
- `diagnose` — Read — https://policylayer.com/tools/design-reprise-reprise/diagnose.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=design-reprise-reprise · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/design-reprise-reprise