// SCAN REPORT

Tracepass

6 tools. 5 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Jul 2026

5 can modify or destroy data

1 read-only

6 tools total

Verified server · catalogue entry verified 02/07/2026 · full schemas captured for 6 of 6 tools

How to control Tracepass ↓

TOOL MAP

What Tracepass exposes to your agents

Read (1) Write / Execute (4) Destructive / Financial (1)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Tracepass costs in tokens

3,008 tokens of tool definitions, loaded on every request

1.5% of a 200k context window

973 heaviest tool: tracepass_passports

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Tracepass tools

Financial · Critical tracepass_passports The tool can commit financial obligations by creating billable DPP slots and triggering overage charges beyond a plan's quota. Write · Medium tracepass_passport_parties The tool creates or modifies economic-operator party records on a passport (set) and removes them (remove/clear). Write · High tracepass_passport_fields This tool creates or modifies data reversibly—it updates existing passport fields rather than reading, executing code, or irreversibly deleting data. Write · Medium tracepass_products The tool spans Read (list, get) and Write (create, update) categories.

5 of Tracepass's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Tracepass

PolicyLayer is an MCP gateway — it sits between your AI agents and Tracepass, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "tracepass_passports": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Rate limit write operations

{
  "tracepass_epcis": {
    "limits": [
      {
        "counter": "tracepass_epcis_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "tracepass_templates": {
    "limits": [
      {
        "counter": "tracepass_templates_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Tracepass — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TRACEPASS →

Instant setup, no code required.

FULL CATALOGUE

All 6 Tracepass tools

FINANCIAL 1 tools

Financial tracepass_passports Manage Digital Product Passports — create, read, and run lifecycle actions. IMPORTANT: create consumes a DPP

WRITE 4 tools

Write tracepass_epcis GS1 EPCIS 2.0 supply-chain events. export is included on Starter plans and up; capture, capture_job, and query Write tracepass_passport_fields Update field values on a Digital Product Passport. Every change is recorded in the passport's audit trail, tag Write tracepass_passport_parties Manage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distrib Write tracepass_products Manage the TracePass product catalogue. A product is the catalogue layer — one product can have many passports

READ 1 tools

Read tracepass_templates Discover the regulatory field schema for each DPP category — what a COMPLIANT passport must contain, per the g

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Tracepass

Can an AI agent move money through the Tracepass MCP server? +

Yes. The Tracepass server exposes 1 financial tools including tracepass_passports. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

How do I prevent bulk modifications through Tracepass? +

The Tracepass server has 4 write tools including tracepass_epcis, tracepass_passport_fields, tracepass_passport_parties. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Tracepass.

How many tools does the Tracepass MCP server expose? +

6 tools across 3 categories: Destructive, Read, Write. 1 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Tracepass? +

Register the Tracepass MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Tracepass tool call.

Deterministic rules across all 6 Tracepass tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TRACEPASS →

Instant setup, no code required.

6 Tracepass tools catalogued and risk-classified — across an index of 43,000+ MCP servers.