Get a single draft order by ID. Returns full draft order including line_items, customer, address, and applied discounts.
AI agents call get_draft_order to retrieve information from Sapo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns data about an existing draft order without creating, modifying, deleting, or executing any operations. It is a standard read operation with minimal security risk—the blast radius is limited to potential exposure of order data if an agent misuses access controls, but no data is altered or destructive actions taken.
From the tool's definition Tool name and description indicate retrieval of a draft order: 'Get a single draft order by ID. Returns full draft order including line_items, customer, address, and applied discounts.' The word 'Get' and 'Returns' confirm this is a read-only query operation…
Documented attack patterns abuse exactly the kind of access get_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 get_draft_order:
{
"version": "1",
"default": "deny",
"tools": {
"get_draft_order": {}
}
}get_draft_order is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a single draft order by ID. Returns full draft order including line_items, customer, address, and applied discounts. It is categorised as a Read tool in the Sapo MCP Server, which means it retrieves data without modifying state.
Register the Sapo MCP server in PolicyLayer and add a rule for get_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.
get_draft_order is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.