Manage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg. Each party carries a legal name and ideally a validated 13-digit GS1 GLN. Actions (pass via action, with args): - set — args: { id, role, legalN...
AI agents use tracepass_passport_parties 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 | Set (add/replace) or remove an economic-operator party on a passport by its role. |
Parameters from the server's own tool schema.
The tool creates or modifies economic-operator party records on a passport (set) and removes them (remove/clear). While 'remove' sounds destructive, it clears a role assignment rather than permanently deleting an irreversible record — roles can be re-assigned. The most severe applicable category is Write.
From the tool's definition 'set — Sets or updates one role' and 'remove — args: { id, role }. Clears one role.' — both actions modify passport party data (economic-operator assignments), which is reversible (a role can be re-set or re-cleared).
Attacks that exploit this kind of access
Manage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg. Each party carries a legal name and ideally a validated 13-digit GS1 GLN. Actions (pass via action, with args): - set — args: { id, role, legalName, gln?, country?, legacyOperatorId? }. Sets or updates one role. - remove — args: { id, role }. Clears one role. 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_parties 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_parties: 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_parties 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_parties 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_parties. 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_parties 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 →