Get sales summary statistics. Aggregate sales data by date range, product, department, or payment method.
AI agents call sales_summary to retrieve information from Bakery Data 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 and returns historical sales aggregate data without creating, modifying, or deleting any records. It poses minimal risk—an AI agent misuse would at worst expose existing business metrics. There is no financial transaction processing, code execution, or data destruction. The tool is explicitly described as 'get' (retrieve) with aggregation, which is characteristic of Read category operations.
From the tool's definition Tool retrieves and aggregates sales data ('Get sales summary statistics', 'Aggregate sales data') with no modification, deletion, or execution capability. It is a read-only analytical query returning summary statistics.
Attacks that exploit this kind of access
Get sales summary statistics. Aggregate sales data by date range, product, department, or payment method. It is categorised as a Read tool in the Bakery Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bakery Data MCP Server MCP server in PolicyLayer and add a rule for sales_summary: 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 Bakery Data MCP Server. Nothing to install.
sales_summary 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 sales_summary 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 sales_summary. 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.
sales_summary is provided by the Bakery Data MCP Server MCP server (t2hnd/bakery_data_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 →