create_delivery
Create a new file delivery (draft \u2014 not visible to client until sent via send_delivery). Requires a paid subscription. Returns the new delivery ID and public slug. Valid statuses: draft \u2192 sent \u2192 approved.
This record as markdown: /tools/app-businys-mcp-server/create-delivery.md
What create_delivery does on Businys
AI agents use create_delivery to create or update resources in Businys, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Businys environment.
Why create_delivery is rated Medium
This tool creates a new deliverable record and manages its lifecycle through reversible state changes. While it does require a paid subscription (suggesting business importance), it does not delete data irreversibly, execute arbitrary code, move funds, or perform read-only operations. It fits the Write category as it creates and modifies data that can be edited or reversed.
From the tool's definition Tool description states 'Create a new file delivery' and tracks state transitions (draft → sent → approved), indicating it creates and modifies data reversibly.
Attacks that exploit this kind of access
The rule that runs create_delivery safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_delivery, this is the rule to start with:
create_delivery stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every create_delivery call is checked against it from then on.
Questions about create_delivery
Create a new file delivery (draft \u2014 not visible to client until sent via send_delivery). Requires a paid subscription. Returns the new delivery ID and public slug. Valid statuses: draft \u2192 sent \u2192 approved. It is categorised as a Write tool in the Businys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Businys MCP server in PolicyLayer and add a rule for create_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 Businys. Nothing to install.
create_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 create_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 create_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.
create_delivery is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue