List the caller's personal inventory items. Authenticated. Required OAuth scope: inventory:read (or pass an api_key for legacy/programmatic clients). Use this when the user asks "what do I own?", "what's on my wishlist?", "what am I selling?", etc. The returned rows include every status by defaul...
Risk signalsHandles credentials or secrets (api_key)
Part of the Partle server.
Free to start. No card required.
AI agents call get_my_inventory to retrieve information from Partle without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_my_inventory only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_my_inventory": {}
}
}See the full Partle policy for all 21 tools.
These attack patterns abuse exactly the kind of access get_my_inventory gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List the caller's personal inventory items. Authenticated. Required OAuth scope: inventory:read (or pass an api_key for legacy/programmatic clients). Use this when the user asks "what do I own?", "what's on my wishlist?", "what am I selling?", etc. The returned rows include every status by default; pass status to filter. Args: status: Filter by lifecycle. One of: owned, wanted, for_sale, sold, discarded. Omit for all. product_id: Filter to rows linked to a specific Partle product. project: Exact-match filter on the project tag. q: Substring search on name and notes (case-insensitive). limit: Page size, 1–200. Default 50. offset: Pagination offset. Default 0. api_key: Legacy/fallback auth. Omit when using OAuth. Returns: {"items": [...], "count": int} where each item carries status, quantity, name (or linked product), notes, prices, etc. On auth failure: {"error": ...}.. It is categorised as a Read tool in the Partle MCP Server, which means it retrieves data without modifying state.
Register the Partle MCP server in PolicyLayer and add a rule for get_my_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 Partle. Nothing to install.
get_my_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_my_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_my_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_my_inventory is provided by the Partle MCP server (https://partle.rubenayla.xyz/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Partle tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.