Search ground-transport connections — bus/coach, rail, or ferry — between two cities (or stations) on a given date, powered by Distribusion. WHEN TO USE THIS TOOL: - The user wants to travel between two places by train, bus/coach, or ferry. - Examples: "trains from Paris to London", "bus from Ber...
Risk signalsHigh parameter count (10 properties)
Part of the Jinko MCP server.
Free to start. No card required.
AI agents call find_ground to retrieve information from Jinko MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though find_ground only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"find_ground": {}
}
}See the full Jinko MCP policy for all 8 tools.
These attack patterns abuse exactly the kind of access find_ground gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search ground-transport connections — bus/coach, rail, or ferry — between two cities (or stations) on a given date, powered by Distribusion. WHEN TO USE THIS TOOL: - The user wants to travel between two places by train, bus/coach, or ferry. - Examples: "trains from Paris to London", "bus from Berlin to Prague tomorrow", "ferry Barcelona to Palma next week". - Provide both a departure and an arrival (city codes preferred, e.g. PAR, LON) and a departure date. INPUTS: - departure_city / arrival_city: IATA-style city codes (PAR, LON, BER). Preferred for chat. - departure_stations / arrival_stations: exact Distribusion station codes when known. - departure_date (required, YYYY-MM-DD, today or later); return_date optional for round trips. - passengers: number of travelers (default 1). The tool returns a list of connections with carrier, transport mode, stations, times, duration, and a "from" price (carrier currency — final fare and fees are confirmed at checkout). Cost: 1 credit per call.. It is categorised as a Read tool in the Jinko MCP MCP Server, which means it retrieves data without modifying state.
Register the Jinko MCP server in PolicyLayer and add a rule for find_ground: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Jinko MCP. Nothing to install.
find_ground is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the find_ground rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for find_ground. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
find_ground is provided by the Jinko MCP server (https://mcp.gojinko.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Jinko MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.