// SCAN REPORT

Jinko MCP

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

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

Last updated: 18 Sept 2026

3 can modify or destroy data

4 read-only

7 tools total

Community server · catalogue entry checked 18/09/2026 · full schemas captured for 7 of 7 tools

How to control Jinko MCP ↓

TOOL MAP

What Jinko MCP exposes to your agents

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

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Jinko MCP costs in tokens

24,279 tokens of tool definitions, loaded on every request

12% of a 200k context window

6,594 heaviest tool: flight_search

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Jinko MCP tools

Destructive · High trip Unified tool for managing a trip (shopping cart). Supports flights and hotels in the same cart. Actions are determined by which objects you Write · Medium flight_calendar Search flights between a known origin and destination using cached pricing. Use this tool whenever the user specifies BOTH where they are fl Write · Medium book Unified tool for booking a trip. Actions are determined by which object you provide. SCHEMA: { create?: { // Initiat

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

POLICY

How to control Jinko MCP

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

Deny destructive operations

{
  "trip": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "book": {
    "limits": [
      {
        "counter": "book_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find_destination": {
    "limits": [
      {
        "counter": "find_destination_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 Jinko 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 JINKO →

Instant setup, no code required.

FULL CATALOGUE

All 7 Jinko MCP tools

DESTRUCTIVE 1 tools

Destructive trip Unified tool for managing a trip (shopping cart). Supports flights and hotels in the same cart. Actions are de

WRITE 2 tools

Write book Unified tool for booking a trip. Actions are determined by which object you provide. SCHEMA: { create?: { Write flight_calendar Search flights between a known origin and destination using cached pricing. Use this tool whenever the user sp

READ 4 tools

Read find_destination Discover travel destinations when the user does NOT know where to go. This is a destination EXPLORATION tool. Read flight_search Live flight tool with two modes. EACH CALL HITS LIVE PRICING — it prices ONE exact date pair, so any loose, op Read hotel_details Rich metadata (gallery, facilities, policies, per-room details) for a single hotel — called by the hotel widge Read hotel_search Search live hotel inventory and rates worldwide. REQUIRED: - destination: object — two distinct modes. Mode A

EXPLORE

Related servers

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

FAQ

Questions about Jinko MCP

Can an AI agent delete data through the Jinko MCP server? +

Yes. The Jinko MCP server exposes 1 destructive tools including trip. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Jinko MCP? +

The Jinko MCP server has 2 write tools including book, flight_calendar. 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 Jinko MCP.

How many tools does the Jinko MCP server expose? +

7 tools across 3 categories: Destructive, Read, Write. 4 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Jinko MCP? +

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

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

ENFORCE POLICY ON JINKO →

Instant setup, no code required.

7 Jinko MCP tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Jinko's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →