Low Risk

tool_search_connections

Search for train connections between two stations.

How to control tool_search_connections ↓

What tool_search_connections does on Koleo MCP Server

AI agents call tool_search_connections to retrieve information from Koleo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why tool_search_connections needs a policy

This tool retrieves or queries public train schedule information between stations. It has no side effects—it does not create, modify, delete data, execute code, or move money. The broader server context (Polish train timetables, departures, arrivals, seat availability) confirms this is informational data access.

From the tool's definition Tool name 'tool_search_connections' and description 'Search for train connections between two stations' indicate a query operation that retrieves timetable data without modifying, deleting, or executing external operations.

Documented attack patterns abuse exactly the kind of access tool_search_connections gives an agent:

How to control tool_search_connections

PolicyLayer is an MCP gateway — it sits between your AI agents and Koleo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for tool_search_connections:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "tool_search_connections": {}
  }
}

tool_search_connections is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Koleo MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about tool_search_connections

What does the tool_search_connections tool do? +

Search for train connections between two stations. It is categorised as a Read tool in the Koleo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tool_search_connections? +

Register the Koleo MCP Server MCP server in PolicyLayer and add a rule for tool_search_connections: 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 Koleo MCP Server. Nothing to install.

What risk level is tool_search_connections? +

tool_search_connections is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tool_search_connections? +

Yes. Add a rate_limit block to the tool_search_connections 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.

How do I block tool_search_connections completely? +

Set action: deny in the PolicyLayer policy for tool_search_connections. 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.

What MCP server provides tool_search_connections? +

tool_search_connections is provided by the Koleo MCP Server MCP server (mbratkowski/koleo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Koleo MCP Server tool call.

Start from Koleo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 Koleo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.