Use this tool to check what information is still missing from the customer before a refund can be processed, and to get a suggested next question to ask. Common use-cases include: - Deciding which piece of context to ask for next (store URL, invoice, reason, bank confirmation) - Surfacing blocker...
AI agents call collect_refund_info 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 reads and evaluates the current state of a refund case to determine what information is missing and what question to ask next. It does not modify data, execute commands, or process any financial transaction — it is purely an informational/advisory tool that guides the agent on next steps.
From the tool's definition 'check what information is still missing', 'Deciding which piece of context to ask for next', 'Knowing when the case is fully collected'
Attacks that exploit this kind of access
Use this tool to check what information is still missing from the customer before a refund can be processed, and to get a suggested next question to ask. Common use-cases include: - Deciding which piece of context to ask for next (store URL, invoice, reason, bank confirmation) - Surfacing blockers such as an Upcoming bill or a plan still on paid, with an explanation the agent can relay to the customer - Knowing when the case is fully collected and ready for. 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 collect_refund_info: 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.
collect_refund_info 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 collect_refund_info 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 collect_refund_info. 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.
collect_refund_info 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 →