Create a new product listing on Partle. Authenticated. Prefer OAuth: connect once via the consent flow on claude.ai (or any MCP client that supports OAuth) and the bearer token is attached automatically — no api_key parameter needed. Fallback: pass an api_key (prefix pk_, generate at /account) fo...
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (api_key)
Part of the Partle server.
Free to start. No card required.
AI agents use create_product 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 create_product 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": {
"create_product": {
"limits": [
{
"counter": "create_product_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 create_product 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.
Create a new product listing on Partle. Authenticated. Prefer OAuth: connect once via the consent flow on claude.ai (or any MCP client that supports OAuth) and the bearer token is attached automatically — no api_key parameter needed. Fallback: pass an api_key (prefix pk_, generate at /account) for programmatic or non-OAuth clients. Required OAuth scope: products:write. Use when the user wants to add an item for sale. For edits to an existing product, use update_product instead. Images. This tool creates text fields only — no image arg. Do not try to pass image bytes through a tool argument; phone-sized payloads blow past conversation context limits. The response includes a one-shot upload_url (signed, ~15 min TTL, bound to this product and your authenticated user). To attach an image from your code-execution sandbox, do one PUT request — no auth headers needed, the URL itself carries the credential: requests.put(result["upload_url"], data=open("/path/to/photo.jpg", "rb").read(), headers={"Content-Type": "image/jpeg"}) The bytes flow Python → HTTP body → Partle, never through the conversation. The URL works once and expires fast. Alternative if you don't have local bytes but have a public image URL: call upload_product_image(product_id, image_url=...) instead. Duplicate prevention. Same user, same product name (case- and whitespace-insensitive) returns 409 with existing.id, existing.url, and a fresh upload_url for that existing product — so if the user is just retrying with a photo, you can attach it directly to the existing listing without having to create or pick anything new. You can also call update_product to change fields. Don't retry blindly. Idempotency. Pass idempotency_key (any unique string per logical create — UUID or hash of the source listing) and a retry after a network failure returns the original response instead of creating a duplicate. Reusing a key with a different payload is a 422. Args: name: Product name. Required, 1–200 chars. description: Long-form product description. Optional. price: Price in whole currency units, not cents (e.g. 15.99 means €15.99). Max 100000. Omit for "ask the seller". currency: Currency symbol. Defaults to €. Use $, £, etc. url: Link to the merchant's product page. Optional but recommended. store_id: ID of the store this product belongs to. Omit for a personal listing not tied to any store. idempotency_key: Optional retry-safety token. Unique per logical create. Send the same key on retries to get the same response. api_key: Legacy/fallback auth. Omit when using OAuth. Returns: The created product record including its new id and canonical partle_url. Share partle_url with the user. Returns {"error": ...} on auth, dedup, or validation failure (dedup also returns {"existing": {"id", "name", "url"}}).. 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 create_product: 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.
create_product 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 create_product 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 create_product. 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.
create_product 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.