// SCAN REPORT

LeadClaw MCP

3 tools. 1 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 3 Jul 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 03/07/2026

How to control LeadClaw MCP ↓

TOOL MAP

What LeadClaw MCP exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous LeadClaw MCP tools

Financial · High book_appointments The tool description explicitly states a financial transaction occurs ('you pay only per confirmed meeting'), meaning invoking this tool commits the user to paying for each confirmed appointment generated.

1 of LeadClaw MCP's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control LeadClaw MCP

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

Block financial tools by default

{
  "book_appointments": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Cap read operations

{
  "check_status": {
    "limits": [
      {
        "counter": "check_status_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 LeadClaw MCP — 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 LEADCLAW →

Instant setup, no code required.

FULL CATALOGUE

All 3 LeadClaw MCP tools

FINANCIAL 1 tools

Financial book_appointments Request confirmed sales appointments delivered to your calendar. Human SDRs handle outbound; you pay only per

READ 2 tools

Read check_status Check the progress of a LeadClaw appointment request. Returns current phase (processing / matching / in_progre Read get_appointment_details Pull full briefing on a specific confirmed appointment: contact info, company context, full BANT breakdown, SD

FAQ

Questions about LeadClaw MCP

Can an AI agent move money through the LeadClaw MCP server? +

Yes. The LeadClaw MCP server exposes 1 financial tools including book_appointments. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How many tools does the LeadClaw MCP server expose? +

3 tools across 2 categories: Read, Write. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on LeadClaw MCP? +

Register the LeadClaw 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 LeadClaw MCP tool call.

Deterministic rules across all 3 LeadClaw MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON LEADCLAW →

Instant setup, no code required.

3 LeadClaw MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.