Token + cost aggregate for a store since a date (defaults to last 30 days). Use for the AI dashboard chart and quota guidance.
AI agents call wafle_ai_usage to retrieve information from wafle 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 read operation that queries historical AI usage metrics and costs. While it accesses financial information (token costs), it does not move money, create charges, or modify any data—it only retrieves aggregate analytics for monitoring purposes.
From the tool's definition Tool retrieves 'Token + cost aggregate for a store since a date' with no modification or deletion of data. The verb is implicit retrieval/query of existing metrics.
Attacks that exploit this kind of access
Token + cost aggregate for a store since a date (defaults to last 30 days). Use for the AI dashboard chart and quota guidance. It is categorised as a Read tool in the wafle MCP server MCP Server, which means it retrieves data without modifying state.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_ai_usage: 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 wafle MCP server. Nothing to install.
wafle_ai_usage 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 wafle_ai_usage 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 wafle_ai_usage. 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.
wafle_ai_usage is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-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 →