Mark an inventory item as sold (status=sold). Convenience wrapper over update_inventory_item for the natural "I sold the drill" request. Authenticated. Required OAuth scope: inventory:write. Caller must own the item. Args: item_id: ID of the inventory row. api_key: Legacy/fallback auth. Returns: ...
Risk signalsHandles credentials or secrets (api_key)
Part of the Partle server.
Free to start. No card required.
AI agents use mark_sold to create or modify resources in Partle. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call mark_sold repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Partle.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"mark_sold": {
"limits": [
{
"counter": "mark_sold_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Partle policy for all 21 tools.
These attack patterns abuse exactly the kind of access mark_sold gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Mark an inventory item as sold (status=sold). Convenience wrapper over update_inventory_item for the natural "I sold the drill" request. Authenticated. Required OAuth scope: inventory:write. Caller must own the item. Args: item_id: ID of the inventory row. api_key: Legacy/fallback auth. Returns: The updated inventory row, or {"error": ...}.. It is categorised as a Write tool in the Partle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Partle MCP server in PolicyLayer and add a rule for mark_sold: 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.
mark_sold is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mark_sold 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 mark_sold. 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.
mark_sold 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.