Retrieve details of a specific order (subscription or payment plan schedule). Returns: payment_next_date (Unix timestamp of next charge), unit (day/week/month/quarter/year), count (units between payments), cc_id (card on file ID), offer_id (needed for update_order), next_sub (subtotal), next_char...
AI agents call get_order to retrieve information from Ontraport MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves order and subscription information without modifying, deleting, or executing any transactions. Although the returned data includes financial details (payment amounts, next charge dates, card references), the tool itself performs no financial operations—it only queries existing order data. Therefore, it is classified as Read rather than Financial.
From the tool's definition Tool name is 'get_order' and description states 'Retrieve details of a specific order' with no modification or deletion capabilities. Returns read-only financial data including payment dates, card IDs, charges, and transaction details.
Attacks that exploit this kind of access
Retrieve details of a specific order (subscription or payment plan schedule). Returns: payment_next_date (Unix timestamp of next charge), unit (day/week/month/quarter/year), count (units between payments), cc_id (card on file ID), offer_id (needed for update_order), next_sub (subtotal), next_charge (total with tax/shipping), transactions_remaining (0 for subscriptions, >0 for payment plans), status (0=current, 1=past due), and shipping address fields. It is categorised as a Read tool in the Ontraport MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ontraport MCP Server MCP server in PolicyLayer and add a rule for get_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 Ontraport MCP Server. Nothing to install.
get_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_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_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_order is provided by the Ontraport MCP Server MCP server (landonray/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 →