// SCAN REPORT

PageFly Refund MCP Server

11 tools. 5 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 3 Jul 2026

5 can modify or destroy data

6 read-only

11 tools total

Community server · catalogue entry verified 03/07/2026

How to control PageFly Refund MCP Server ↓

TOOL MAP

What PageFly Refund MCP Server exposes to your agents

Read (6) Write / Execute (3) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous PageFly Refund MCP Server tools

Financial · High calculate_refund This tool directly computes financial obligations—refund amounts—which represents a commitment of money back to customers. Financial · Critical classify_refund_case Use this tool to classify a refund request into one of the 8 playbook cases (TH1 to TH8) and get back the recommended action, deduct Write · Medium generate_refund_message This tool generates/drafts a message to be sent to a customer. Write · High save_case_state This tool modifies case state records in the Turso/libSQL database.

5 of PageFly Refund MCP Server's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control PageFly Refund MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and PageFly Refund MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "calculate_refund": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations

{
  "generate_refund_message": {
    "limits": [
      {
        "counter": "generate_refund_message_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_subscription": {
    "limits": [
      {
        "counter": "check_subscription_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register PageFly Refund MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PAGEFLY REFUND →

Instant setup, no code required.

FULL CATALOGUE

All 11 PageFly Refund MCP Server tools

FINANCIAL 2 tools

Financial calculate_refund Use this tool to compute the refund amount a customer should receive, following PageFly Financial classify_refund_case Use this tool to classify a refund request into one of the 8 playbook cases (TH1 to TH8) and get back

WRITE 3 tools

Write generate_refund_message Use this tool to draft the reply that will be sent to the customer, combining the PageFly refund templ Write save_case_state Use this tool to persist (create or update) the state of a refund case so that it can be resumed in a Write tag_case Use this tool to attach the

READ 6 tools

Read check_subscription Use this tool to retrieve a customer Read check_usage_data Use this tool to check whether a store actively USED PageFly during a billing period — i.e. whether it Read collect_refund_info Use this tool to check what information is still missing from the customer before a refund can be proc Read get_billing_history Use this tool to retrieve the full billing history of a Shopify store on PageFly, including all charge Read get_case_state Use this tool to load the persisted state of a refund case by store URL. This is the first thing to ca Read list_pending_cases Use this tool to list refund cases ordered by most recent activity, optionally filtered by stage.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about PageFly Refund MCP Server

Can an AI agent move money through the PageFly Refund MCP Server MCP server? +

Yes. The PageFly Refund MCP Server server exposes 2 financial tools including calculate_refund, classify_refund_case. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through PageFly Refund MCP Server? +

The PageFly Refund MCP Server server has 3 write tools including generate_refund_message, save_case_state, tag_case. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach PageFly Refund MCP Server.

How many tools does the PageFly Refund MCP Server MCP server expose? +

11 tools across 3 categories: Financial, Read, Write. 6 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on PageFly Refund MCP Server? +

Register the PageFly Refund MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every PageFly Refund MCP Server tool call.

Deterministic rules across all 11 PageFly Refund MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PAGEFLY REFUND →

Instant setup, no code required.

11 PageFly Refund MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.