// SCAN REPORT

WikiTree MCP server

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

1 write tool that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

1 can modify or destroy data

4 read-only

5 tools total

Community server · catalogue entry verified 30/06/2026

How to control WikiTree MCP server ↓

TOOL MAP

What WikiTree MCP server exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous WikiTree MCP server tools

Execute · High call_api This tool allows calling any arbitrary WikiTree API endpoint, not just read operations.

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

POLICY

How to control WikiTree MCP server

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

Cap read operations

{
  "get_ancestors": {
    "limits": [
      {
        "counter": "get_ancestors_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 WikiTree MCP server — 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 WIKITREE →

Instant setup, no code required.

FULL CATALOGUE

All 5 WikiTree MCP server tools

EXECUTE 1 tools

Execute call_api Call any WikiTree API endpoint directly

READ 4 tools

Read get_ancestors Retrieve ancestors for a given person ID Read get_descendants Retrieve descendants for a given person ID Read get_person Retrieve a single person record from WikiTree Read get_relatives Retrieve relatives for a given person ID or list of IDs

FAQ

Questions about WikiTree MCP server

Is the WikiTree MCP server MCP server safe to use without restrictions? +

The WikiTree MCP server server is primarily read-only with 4 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the WikiTree MCP server MCP server expose? +

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

How do I enforce a policy on WikiTree MCP server? +

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

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

ENFORCE POLICY ON WIKITREE →

Instant setup, no code required.

5 WikiTree MCP server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.