Manage the TracePass product catalogue. A product is the catalogue layer — one product can have many passports (one per serialised unit). Products are not billable on their own. Actions (pass via action, with args): - list — args: { page?, limit? (≤100), category?, status?, search? }. Read-only. ...
AI agents use tracepass_products to create or update resources in Tracepass — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tracepass environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
args | object | — | Arguments for the chosen action; required fields depend on `action` (see each action above). |
action | string | Yes | Which product operation to run: list | get | create | update. |
Parameters from the server's own tool schema.
The tool spans Read (list, get) and Write (create, update) categories. The create and update actions modify product catalogue data reversibly without deletion or financial implications. This qualifies as Write.
From the tool's definition Tool description explicitly lists 'create' and 'update' actions that modify data: 'create — args: { name, model, category, description? }' and 'update — args: { id, name?, model?, description? }'.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Manage the TracePass product catalogue. A product is the catalogue layer — one product can have many passports (one per serialised unit). Products are not billable on their own. Actions (pass via action, with args): - list — args: { page?, limit? (≤100), category?, status?, search? }. Read-only. - get — args: { id }. Read-only. - create — args: { name, model, category, description? }. category is one of: battery, textile, electronics, construction, steel, chemicals, packaging, furniture, tyres, jewelry, toys, fmcg. - update — args: { id, name?, model?, description? }; pass at least one field to change. It is categorised as a Write tool in the Tracepass MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
tracepass_products accepts 2 parameters: args, action. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Tracepass MCP server in PolicyLayer and add a rule for tracepass_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 Tracepass. Nothing to install.
tracepass_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 tracepass_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 tracepass_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.
tracepass_products is provided by the Tracepass MCP server (https://ai.tracepass.eu/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 →