// SCAN REPORT

KMB Bus

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

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
5 read-only
5 tools total
// TOOL MAP
Read (5) Write / Execute (0) Destructive / Financial (0)
// WHAT CAN GO WRONG
✕

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

// RECOMMENDED RULES
Cap read operations
find_buses_to_destination:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 5 KMB BUS TOOLS
READ 5 tools
Read find_buses_to_destination Read find_stop_by_name Read get_all_routes_at_stop Read get_next_bus Read get_route_stops_info
// FAQ
Is the KMB Bus MCP server safe to use without restrictions? +

The KMB Bus server is primarily read-only with 5 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 KMB Bus MCP server expose? +

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

How do I add Intercept to my KMB Bus setup? +

One line change. Instead of running the KMB Bus server directly, prefix it with Intercept: intercept -c kennyckk-mcp-hkbus.yaml -- npx -y @kennyckk/mcp_hkbus. Download a pre-built policy from policylayer.com/policies/kennyckk-mcp-hkbus and adjust the limits to match your use case.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.