Query POS transaction data. Supports filtering by date range, product code/name, payment method, and amount range. Returns transaction details.
AI agents call query_transactions 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 retrieves transaction records from the bakery POS system with various filter options, but performs no side effects or modifications. It is purely a read operation. Severity is medium (not low) because transaction data may contain sensitive payment information, customer details, or financial records that could be misused if an agent queries and exfiltrates it without authorization.
From the tool's definition Tool description states 'Query POS transaction data' with filtering and returns transaction details. The verb 'Query' and 'Returns' indicate data retrieval with no modification capability. No language about creating, deleting, executing, or modifying data.
Attacks that exploit this kind of access
Query POS transaction data. Supports filtering by date range, product code/name, payment method, and amount range. Returns transaction details. 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 query_transactions: 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.
query_transactions 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 query_transactions 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 query_transactions. 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.
query_transactions 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.
query_transactions is one line of Bakery Data MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →