Load one inventory from Sanka by inventory id, numeric id, or external reference.
AI agents call get_inventory to retrieve information from Sanka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'Load' combined with the retrieval-only parameters (id-based lookups) clearly indicates this is a query operation that retrieves existing inventory data. There is no indication of data modification, deletion, code execution, or financial impact. This is a standard Read operation with minimal risk even if misused by an AI agent, as it only exposes existing inventory information.
From the tool's definition Tool name 'get_inventory' and description 'Load one inventory from Sanka by inventory id, numeric id, or external reference' indicates retrieval of data without modification or side effects.
Attacks that exploit this kind of access
Load one inventory from Sanka by inventory id, numeric id, or external reference. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for get_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 Sanka MCP Server. Nothing to install.
get_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 get_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 get_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.
get_inventory is provided by the Sanka MCP Server MCP server (sankahq/sanka-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 →