Use this tool to check whether a store actively USED PageFly during a billing period — i.e. whether it has pages published or recently edited. Call it when a customer claims
AI agents call check_usage_data 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 queries historical usage data to determine if a customer actually used the service during a billing period. It is purely informational—it reads data to support refund decision-making but does not create, modify, delete, or execute any operations.
From the tool's definition The tool 'check_usage_data' is described as checking whether a store 'actively USED PageFly during a billing period' by examining if it 'has pages published or recently edited.' It retrieves or queries data about usage metrics with no side effects.
Attacks that exploit this kind of access
Use this tool to check whether a store actively USED PageFly during a billing period — i.e. whether it has pages published or recently edited. Call it when a customer claims. 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 check_usage_data: 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.
check_usage_data 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 check_usage_data 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 check_usage_data. 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.
check_usage_data 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 →