AI agents use sendle_create_order to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
sender | object | Yes | |
api_key | string | — | |
receiver | object | Yes | |
parcel_contents | array | — |
Parameters from the server's own tool schema.
The tool creates (writes) a new shipping order in the Sendle system. This is reversible in principle (orders can be cancelled), so it is Write rather than Destructive. However, it affects real-world logistics and may incur financial costs (shipping fees), warranting high severity due to potential for misuse by an AI agent (e.g., creating fraudulent or erroneous orders at scale).
From the tool's definition Tool name 'sendle_create_order' and description 'Create a Sendle shipping order' indicate creation of a shipping order record. Sendle is a logistics/shipping platform, so this creates a new order in an external system.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
Create a Sendle shipping order. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sendle_create_order accepts 4 parameters: sender, api_key, receiver, parcel_contents. Required: sender, receiver. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for sendle_create_order: 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 UnClick. Nothing to install.
sendle_create_order 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 sendle_create_order 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 sendle_create_order. 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.
sendle_create_order is provided by the UnClick MCP server (@unclick/mcp-server). 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 →