// SCAN REPORT

Handshake

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

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

Last updated: 3 Jul 2026

1 can modify or destroy data

8 read-only

9 tools total

Community server · catalogue entry verified 03/07/2026

How to control Handshake ↓

TOOL MAP

What Handshake exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Handshake tools

Write · Medium close_session Close the current browser session and clean up resources.

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

POLICY

How to control Handshake

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

Rate limit write operations

{
  "close_session": {
    "limits": [
      {
        "counter": "close_session_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_employer_profile": {
    "limits": [
      {
        "counter": "get_employer_profile_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 Handshake — 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 HANDSHAKE →

Instant setup, no code required.

FULL CATALOGUE

All 9 Handshake tools

WRITE 1 tools

Write close_session Close the current browser session and clean up resources.

READ 8 tools

Read get_employer_profile get_employer_profile Read get_event_details get_event_details Read get_job_details get_job_details Read get_job_search_filters get_job_search_filters Read get_student_profile get_student_profile Read search_employers search_employers Read search_events search_events Read search_jobs search_jobs

FAQ

Questions about Handshake

How do I prevent bulk modifications through Handshake? +

The Handshake server has 1 write tools including close_session. 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 Handshake.

How many tools does the Handshake MCP server expose? +

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

How do I enforce a policy on Handshake? +

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

Deterministic rules across all 9 Handshake tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON HANDSHAKE →

Instant setup, no code required.

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