plan_delivery · ILP Drone Delivery MCP Server MCP

WHAT IT DOES

What plan_delivery does on ILP Drone Delivery MCP Server

AI agents invoke plan_delivery to trigger actions in ILP Drone Delivery MCP Server. 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 plan_delivery needs a policy

This tool executes a planning operation that assigns drones and computes routes — it triggers external operational logic (drone assignment, route computation) rather than merely reading data. While it may not physically dispatch a drone, it 'plans and assigns' which could initiate or commit resources.

From the tool's definition Plan a delivery route including cost estimate, number of moves, and drone assignment. Returns complete path planning.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

plan_delivery Rate-limited

plan_delivery 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": {
    "plan_delivery": {
      "limits": [
        {
          "counter": "plan_delivery_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 ILP Drone Delivery MCP Server, so you can run agents against it safely.

FAQ

Questions about plan_delivery

What does the plan_delivery tool do? +

Plan a delivery route including cost estimate, number of moves, and drone assignment. Returns complete path planning. It is categorised as a Execute tool in the ILP Drone Delivery MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on plan_delivery? +

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

What risk level is plan_delivery? +

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

Can I rate-limit plan_delivery? +

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

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

plan_delivery is provided by the ILP Drone Delivery MCP Server MCP server (rheabose/ilp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.