Time-series breakdown of analytics: revenue + orders bucketed by day/week/month.\n\n
AI agents call wafle_analytics_by_period 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 tool retrieves and presents historical analytics data in time-series format. It has no side effects—it queries analytics without creating, modifying, deleting, or executing anything. This is a classic Read operation that gathers business intelligence for reporting purposes.
From the tool's definition Tool name 'wafle_analytics_by_period' and description 'Time-series breakdown of analytics: revenue + orders bucketed by day/week/month' indicate data retrieval only.
Attacks that exploit this kind of access
Time-series breakdown of analytics: revenue + orders bucketed by day/week/month.\n\n. 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_analytics_by_period: 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_analytics_by_period 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_analytics_by_period 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_analytics_by_period. 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_analytics_by_period 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 →