start_all_servers · MCP Travel Planner MCP: Risk & Policy

WHAT IT DOES

What start_all_servers does on MCP Travel Planner

AI agents invoke start_all_servers to trigger actions in MCP Travel Planner. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_all_servers needs a policy

Starting servers is an Execute-category action: it runs/triggers external operations whose effects depend on runtime discovery of available servers. The severity is high because launching multiple external services could consume resources, change system state, and trigger cascading side effects across the travel planning infrastructure.

From the tool's definition "Start all discovered travel planner servers" indicates launching external processes or services. The requirement of SERPAPI_KEY suggests interaction with external APIs and systems whose behavior depends on which servers are discovered and started.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_all_servers Rate-limited

start_all_servers stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_all_servers": {
      "limits": [
        {
          "counter": "start_all_servers_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Travel Planner, so you can run agents against it safely.

FAQ

Questions about start_all_servers

What does the start_all_servers tool do? +

Start all discovered travel planner servers (requires SERPAPI_KEY). It is categorised as a Execute tool in the MCP Travel Planner MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_all_servers? +

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

What risk level is start_all_servers? +

start_all_servers is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_all_servers? +

Yes. Add a rate_limit block to the start_all_servers 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 start_all_servers completely? +

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

start_all_servers is provided by the MCP Travel Planner MCP server (leonavevor/mcp_travelassistant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.