AI agents call search_item_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 'search' prefix and inventory context indicate this tool queries or retrieves inventory data without modifying it. Confidence is slightly reduced due to empty description, but the sibling tools' patterns and the read-only nature of search operations in this workflow justify Read classification at low severity.
From the tool's definition Tool name 'search_item_inventory' indicates a search operation. Server context shows inventory management with sibling tools like 'search_items', 'search_trips', and 'lookup_trip_details' that are clearly read-only queries.
Attacks that exploit this kind of access
search_item_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 search_item_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.
search_item_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 search_item_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 search_item_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.
search_item_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 →