Update field values on a Digital Product Passport. Every change is recorded in the passport's audit trail, tagged as an API-key update. Actions (pass via action, with args): - update — args: { id, fieldKey, value }. value type matches the field's dataType (string, number, boolean, array, object)....
AI agents use tracepass_passport_fields 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`. |
action | string | Yes | Update one passport field, addressed by passport id (update) or by your serial (update_by_serial). |
Parameters from the server's own tool schema.
This tool creates or modifies data reversibly—it updates existing passport fields rather than reading, executing code, or irreversibly deleting data. The changes are logged in an audit trail, suggesting they can potentially be reviewed or rolled back.
From the tool's definition The tool explicitly provides an 'update' action that modifies field values on a Digital Product Passport, with changes recorded in an audit trail.
Attacks that exploit this kind of access
Update field values on a Digital Product Passport. Every change is recorded in the passport's audit trail, tagged as an API-key update. Actions (pass via action, with args): - update — args: { id, fieldKey, value }. value type matches the field's dataType (string, number, boolean, array, object). - update_by_serial — args: { serial, fieldKey, value, gtin? }. Same as update, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in your account the call returns 409 ambiguous_serial; pass gtin (or use update by id) to resolve exactly. 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_passport_fields 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_passport_fields: 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_passport_fields 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_passport_fields 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_passport_fields. 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_passport_fields 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 →