Create a new product for inventory management and payment processing on behalf of a merchant (ISV operation). ISV Authentication: Requires ISV credentials and OAuth2 token from target merchant. Product Structure: 📦 PRODUCT METADATA: name, shortDescription, longDescription, sku, upc, shippable, a...
AI agents use payware_products_create_product to create or update resources in Payware MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Payware MCP Server environment.
This tool creates new records (products) in a merchant's system, which is a reversible write operation. While it doesn't move money directly, it creates product catalog entries that feed into payment processing workflows, making it a Write action rather than Financial.
From the tool's definition Tool creates a new product in a merchant's inventory and payment system: 'Create a new product for inventory management and payment processing on behalf of a merchant (ISV operation).' Accepts product metadata including name, description, SKU, pricing data,…
Attacks that exploit this kind of access
Create a new product for inventory management and payment processing on behalf of a merchant (ISV operation). ISV Authentication: Requires ISV credentials and OAuth2 token from target merchant. Product Structure: 📦 PRODUCT METADATA: name, shortDescription, longDescription, sku, upc, shippable, active, shop 💰 PRODUCT DATA (prData object): type, regularPrice, currency, overlapPriority, timeToLive, activeFrom, activeTo, timeZone ⚙️ PRODUCT OPTIONS (prOptions object): imageUrl, termsUrl, termsText Required: merchantPartnerId, oauth2Token, name. It is categorised as a Write tool in the Payware MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Payware MCP Server MCP server in PolicyLayer and add a rule for payware_products_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 Payware MCP Server. Nothing to install.
payware_products_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 payware_products_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 payware_products_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.
payware_products_create_product is provided by the Payware MCP Server MCP server (payware/mcp-server). 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 →