Use this tool to retrieve the full billing history of a Shopify store on PageFly, including all charges, invoice dates, PageFly earnings after Shopify fees, refunded amounts and bill statuses. Common use-cases include: - Verifying how many cycles the customer has actually paid for - Spotting an U...
AI agents call get_billing_history to retrieve information from PageFly Refund MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only operations on billing data. While the data being accessed is sensitive (financial records like charges and refunds), the tool itself does not execute financial transactions, create obligations, delete records, or modify state.
From the tool's definition Tool retrieves billing history including charges, invoice dates, refunded amounts, and bill statuses. The description explicitly uses retrieval language: 'retrieve the full billing history', 'Verifying how many cycles', 'Checking whether a cycle has already…
Attacks that exploit this kind of access
Use this tool to retrieve the full billing history of a Shopify store on PageFly, including all charges, invoice dates, PageFly earnings after Shopify fees, refunded amounts and bill statuses. Common use-cases include: - Verifying how many cycles the customer has actually paid for - Spotting an Upcoming bill (triggers the TH4 App Credit / post-pay refund flow) - Checking whether a cycle has already been refunded before issuing a new one Call this tool after. It is categorised as a Read tool in the PageFly Refund MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PageFly Refund MCP Server MCP server in PolicyLayer and add a rule for get_billing_history: 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 PageFly Refund MCP Server. Nothing to install.
get_billing_history 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_billing_history 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_billing_history. 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_billing_history is provided by the PageFly Refund MCP Server MCP server (nthieu002/refund-crisp-mcp). 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 →