Complete a draft order and convert it into a real order. Side effect: creates an Order from the draft; draft status becomes
AI agents use complete_draft_order to create or update resources in Sapo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sapo environment.
While the tool creates a new order (Write category), it is not Financial because it does not move money or commit financial obligations directly; that would occur in separate payment processing. The creation of an Order is a significant state change but is theoretically reversible through order cancellation/deletion by authorized users.
From the tool's definition Tool description states 'Complete a draft order and convert it into a real order. Side effect: creates an Order from the draft' — this irreversibly creates a new Order entity in the system.
Documented attack patterns abuse exactly the kind of access complete_draft_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sapo, and nothing reaches the server without passing your rules. This is the rule we recommend for complete_draft_order:
{
"version": "1",
"default": "deny",
"tools": {
"complete_draft_order": {
"limits": [
{
"counter": "complete_draft_order_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} complete_draft_order 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.
Free to start. No card required.
Complete a draft order and convert it into a real order. Side effect: creates an Order from the draft; draft status becomes. It is categorised as a Write tool in the Sapo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sapo MCP server in PolicyLayer and add a rule for complete_draft_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 Sapo. Nothing to install.
complete_draft_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 complete_draft_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 complete_draft_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.
complete_draft_order is provided by the Sapo MCP server (nguyennguyenit/sapo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sapo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
93 Sapo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.