complete_delivery
AI agents use complete_delivery to create or update resources in FleetMind MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FleetMind MCP Server environment.
The tool most likely updates delivery/order records to mark them as complete, which is a reversible modification (orders can be reopened/disputed). This is Write category (modifies data) rather than Read (retrieves only), Destructive (would need to purge/delete), or Execute (no external command execution apparent).
From the tool's definition Tool name 'complete_delivery' combined with sibling tools 'create_assignment', 'create_order', and 'create_driver' suggests a delivery fleet management system. 'Complete' implies marking a delivery as finished, which modifies order status.
Attacks that exploit this kind of access
complete_delivery. It is categorised as a Write tool in the FleetMind MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FleetMind MCP Server MCP server in PolicyLayer and add a rule for complete_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 FleetMind MCP Server. Nothing to install.
complete_delivery is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete_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.
Set action: deny in the PolicyLayer policy for complete_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.
complete_delivery is provided by the FleetMind MCP Server MCP server (mashrur-rahman-fahim/fleetmind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →