start_server · MCP Travel Planner MCP: Risk & Policy

WHAT IT DOES

What start_server does on MCP Travel Planner

AI agents invoke start_server 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_server needs a policy

Starting a server is an Execute action: it triggers an external operation (server startup) whose side effects are not automatically reversible and depend on runtime arguments (which server). While not inherently destructive, it grants significant control over infrastructure and could enable downstream harm if a malicious or misconfigured server is started.

From the tool's definition Tool name is 'start_server' with description 'Start a specific travel planner server' — this initiates execution of a server process, which is an external operation whose effects depend on which server is started and what that server does.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_server Rate-limited

start_server 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_server": {
      "limits": [
        {
          "counter": "start_server_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_server

What does the start_server tool do? +

Start a specific travel planner server. 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_server? +

Register the MCP Travel Planner MCP server in PolicyLayer and add a rule for start_server: 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_server? +

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

Can I rate-limit start_server? +

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

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

start_server 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.