receipts.list
AI agents call receipts.list to retrieve information from Kelnix Receipt Mcp Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to list or retrieve receipt records from the server's database. This is a read-only operation with no side effects—it retrieves data without creating, modifying, deleting, or executing code. Even if an AI agent misuses it, the blast radius is minimal since no data is altered and no financial transactions are triggered.
From the tool's definition Tool name 'receipts.list' indicates retrieval/enumeration of receipt data. Description is empty, which limits confidence slightly, but the naming pattern and server context (accounting/receipt processing) suggest this is a query operation returning a list of…
Attacks that exploit this kind of access
receipts.list. It is categorised as a Read tool in the Kelnix Receipt Mcp Api MCP Server, which means it retrieves data without modifying state.
Register the Kelnix Receipt Mcp Api MCP server in PolicyLayer and add a rule for receipts.list: 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 Kelnix Receipt Mcp Api. Nothing to install.
receipts.list 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 receipts.list 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 receipts.list. 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.
receipts.list is provided by the Kelnix Receipt Mcp Api MCP server (kelnixsolutions/kelnix-receipt-mcp-api). 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 →