AI agents call find_expired_inventory to retrieve information from Sana without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to identify or retrieve expired inventory items. Despite the empty description, the name pattern aligns with other Read operations on the server (search_discard_history, search_item_inventory, lookup_trip_details). No evidence of mutation, deletion, or execution. Confidence is moderate due to lack of explicit description, but the tool name strongly indicates a read-only inventory query.
From the tool's definition Tool name 'find_expired_inventory' indicates a search or lookup operation. The empty description provides no explicit confirmation, but the naming pattern (find_*) and context within an inventory management workflow suggests a query operation that retrieves…
Attacks that exploit this kind of access
find_expired_inventory. It is categorised as a Read tool in the Sana MCP Server, which means it retrieves data without modifying state.
Register the Sana MCP server in PolicyLayer and add a rule for find_expired_inventory: 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 Sana. Nothing to install.
find_expired_inventory 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 find_expired_inventory 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 find_expired_inventory. 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.
find_expired_inventory is provided by the Sana MCP server (sana-mcp-server). 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 →