Move an inventory item to status=for_sale and set listing fields. Convenience wrapper over update_inventory_item that matches a natural user request ("list my drill for sale at 30€"). Sets all three columns (status, asking_price, asking_currency, and optionally condition) atomically. Authenticate...
Risk signalsHandles credentials or secrets (api_key)
Part of the Partle server.
Free to start. No card required.
AI agents use mark_for_sale 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_for_sale 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_for_sale": {
"limits": [
{
"counter": "mark_for_sale_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_for_sale 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.
Move an inventory item to status=for_sale and set listing fields. Convenience wrapper over update_inventory_item that matches a natural user request ("list my drill for sale at 30€"). Sets all three columns (status, asking_price, asking_currency, and optionally condition) atomically. Authenticated. Required OAuth scope: inventory:write. Caller must own the item. Args: item_id: ID of the inventory row. asking_price: How much you're asking for it. Whole units, not cents. Required. asking_currency: Currency. Default €. condition: Free string describing the item's condition (e.g. like_new, good). Optional. 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_for_sale: 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_for_sale 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_for_sale 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_for_sale. 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_for_sale 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.