[Developer tool] Sync products from the app's Stripe account and configure which ones agents can discover and sell. Call this after dev_connect_stripe to set up the product catalog. Pass product_ids to enable — all others will be disabled. If product_ids is omitted, syncs and lists all products s...
AI agents use dev_configure_products to create or update resources in Tru — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tru environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
product_ids | array | — | Product IDs to make visible to agents. All others will be hidden. Omit to just list products. |
service_name | string | — | The service_name of the app. If omitted, uses the app from ~/.tru/config.json. |
Parameters from the server's own tool schema.
This tool creates or modifies configuration data (product enablement status) reversibly. While it controls which products are available for agents to sell, it does not execute transactions, delete data irreversibly, or move money directly.
From the tool's definition Tool description states it can 'configure which ones agents can discover and sell' and 'enable' or 'disable' products. This involves modifying the product catalog configuration that affects billing and provisioning behavior.
Attacks that exploit this kind of access
[Developer tool] Sync products from the app's Stripe account and configure which ones agents can discover and sell. Call this after dev_connect_stripe to set up the product catalog. Pass product_ids to enable — all others will be disabled. If product_ids is omitted, syncs and lists all products so the developer can choose. It is categorised as a Write tool in the Tru MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dev_configure_products accepts 2 parameters: product_ids, service_name. The full parameter table on this page comes from the server's own tool schema.
Register the Tru MCP server in PolicyLayer and add a rule for dev_configure_products: 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 Tru. Nothing to install.
dev_configure_products 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 dev_configure_products 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 dev_configure_products. 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.
dev_configure_products is provided by the Tru MCP server (tru-mcp). 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 →