Use this tool to persist (create or update) the state of a refund case so that it can be resumed in a future conversation. Every field except store_url is optional; the tool performs a partial upsert using store_url as the primary key. CALL THIS AFTER EVERY STEP — not just at the end. Each handli...
AI agents use save_case_state to create or update resources in PageFly Refund MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PageFly Refund MCP Server environment.
This tool modifies case state records in the Turso/libSQL database. While the modifications are reversible (upsert operations can be overwritten), the tool is used to record critical refund case decisions and actions. Misuse could result in incorrect case states being persisted, leading to erroneous refund processing.
From the tool's definition The tool description explicitly states it 'persist (create or update) the state of a refund case' and performs 'a partial upsert using store_url as the primary key.' This is a data modification operation that creates or updates records in the persistent…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Use this tool to persist (create or update) the state of a refund case so that it can be resumed in a future conversation. Every field except store_url is optional; the tool performs a partial upsert using store_url as the primary key. CALL THIS AFTER EVERY STEP — not just at the end. Each handling action is a checkpoint that must be persisted with the matching. It is categorised as a Write tool in the PageFly Refund MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PageFly Refund MCP Server MCP server in PolicyLayer and add a rule for save_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.
save_case_state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_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 save_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.
save_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 →