// SCAN REPORT

Claude Handoff

4 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

2 can modify or destroy data

2 read-only

4 tools total

Community server · catalogue entry verified 29/06/2026

How to control Claude Handoff ↓

TOOL MAP

What Claude Handoff exposes to your agents

Read (2) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Claude Handoff tools

Execute · Medium fetch_handoff This tool fetches remote content from a URL and extracts an archive to a temp directory on the local filesystem. Write · High deploy_bundle This tool writes/copies files from an extracted bundle into a local project directory.

2 of Claude Handoff's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Claude Handoff

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Handoff, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "deploy_bundle": {
    "limits": [
      {
        "counter": "deploy_bundle_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "inspect_bundle": {
    "limits": [
      {
        "counter": "inspect_bundle_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Claude Handoff — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON CLAUDE HANDOFF →

Instant setup, no code required.

FULL CATALOGUE

All 4 Claude Handoff tools

EXECUTE 1 tools

Execute fetch_handoff Fetch a Claude Design handoff bundle from its URL and extract it to a temp directory. Supports HTML bundles (g

WRITE 1 tools

Write deploy_bundle Copy an extracted bundle to a local directory (e.g. your project

READ 2 tools

Read inspect_bundle Summarize a previously-fetched handoff bundle: README contents, entry HTML, file type counts, and a preview of Read read_readme Read the full README.md from a fetched handoff bundle. Claude Design handoffs always include a README describi

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Claude Handoff

How do I prevent bulk modifications through Claude Handoff? +

The Claude Handoff server has 1 write tools including deploy_bundle. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Claude Handoff.

How many tools does the Claude Handoff MCP server expose? +

4 tools across 2 categories: Execute, Read. 2 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Claude Handoff? +

Register the Claude Handoff MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Claude Handoff tool call.

Deterministic rules across all 4 Claude Handoff tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON CLAUDE HANDOFF →

Instant setup, no code required.

4 Claude Handoff tools catalogued and risk-classified — across an index of 43,000+ MCP servers.