Use this tool to list refund cases ordered by most recent activity, optionally filtered by stage. Common use-cases include: - Daily review of cases awaiting Manager approval (stage: awaiting_manager) - Finding conversations that went quiet for follow-up (stage: awaiting_customer_confirm) - Gettin...
AI agents call list_pending_cases 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 queries of case data without side effects. It does not create, modify, delete, or execute any operations — it only retrieves and presents existing refund case information. While the refund domain involves financial data, the tool itself does not move money or commit financial obligations; it merely lists cases for review.
From the tool's definition The tool 'list_pending_cases' retrieves and queries refund case data ordered by activity and filtered by stage.
Attacks that exploit this kind of access
Use this tool to list refund cases ordered by most recent activity, optionally filtered by stage. Common use-cases include: - Daily review of cases awaiting Manager approval (stage: awaiting_manager) - Finding conversations that went quiet for follow-up (stage: awaiting_customer_confirm) - Getting an overview of the refund pipeline Results are capped to. 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 list_pending_cases: 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.
list_pending_cases 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 list_pending_cases 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 list_pending_cases. 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.
list_pending_cases 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 →