Use this tool to load the persisted state of a refund case by store URL. This is the first thing to call at the start of a refund conversation so that the AI can see what has already been done (winback offered, breakdown sent, manager status, etc.) and continue seamlessly. Returns null when no ca...
AI agents call get_case_state 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 is a query/retrieval operation with no side effects. It reads case information from persistent storage to enable the AI agent to view prior refund handling context. The tool only accesses data; it does not create, modify, or delete records. While the broader server handles financial operations (refunds), this specific tool is purely informational, making it a Read category with low severity.
From the tool's definition Tool loads and retrieves persisted case state by store URL; description states 'load the persisted state' and 'see what has already been done', with return value being null or existing state data. No modifications, deletions, or side effects occur.
Attacks that exploit this kind of access
Use this tool to load the persisted state of a refund case by store URL. This is the first thing to call at the start of a refund conversation so that the AI can see what has already been done (winback offered, breakdown sent, manager status, etc.) and continue seamlessly. Returns null when no case has been saved yet — in that situation, start a fresh collect_refund_info pass and create the case with save_case_state. 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_case_state: 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_case_state 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_case_state 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_case_state. 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_case_state 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 →