Retrieve detailed purchase history logs showing the lifecycle of individual purchases (created, paid, refunded, etc.).
AI agents call get_purchase_logs 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 or queries historical purchase data without side effects. While Ontraport is a CRM with financial context, this specific tool only reads purchase logs—it does not execute payments, create refunds, modify subscriptions, or commit financial obligations. The verb 'Retrieve' and absence of any modification language confirm it is a Read operation.
From the tool's definition Tool name 'get_purchase_logs' and description 'Retrieve detailed purchase history logs' indicate a read-only operation that queries and returns existing purchase data with no modifications, deletions, or financial transactions.
Attacks that exploit this kind of access
Retrieve detailed purchase history logs showing the lifecycle of individual purchases (created, paid, refunded, etc.). 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_purchase_logs: 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_purchase_logs 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_purchase_logs 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_purchase_logs. 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_purchase_logs 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 →