peppol_lookup
utilpeek: Check whether a company is registered on the Peppol e-invoicing network. For the legal entity use search_lei. Returns whether a Peppol participant ID (such as 0192:983887457) is registered on the Peppol e-invoicing network, from its SML DNS record; if so, its SMP URL and the document ty...
This record as markdown: /tools/dev-tanod-tanod/peppol-lookup.md
What peppol_lookup does on Tanod
AI agents call peppol_lookup to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
scheme | string | — | Identifier scheme. Only iso6523-actorid-upis (the default) is supported. |
participant | string | Yes | Peppol participant ID: a four-digit ICD, a colon and the identifier (1-50 of letters, digits, '.', '_', '-'), such as 0192:983887457 (a Norwegian organisation n |
Parameters from the server's own tool schema.
Why peppol_lookup is rated Low
Even though peppol_lookup only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs peppol_lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For peppol_lookup, this is the rule to start with:
peppol_lookup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every peppol_lookup call is checked against it from then on.
Questions about peppol_lookup
utilpeek: Check whether a company is registered on the Peppol e-invoicing network. For the legal entity use search_lei. Returns whether a Peppol participant ID (such as 0192:983887457) is registered on the Peppol e-invoicing network, from its SML DNS record; if so, its SMP URL and the document types the SMP lists (BIS Billing 3.0 invoice and credit note, order, despatch advice and invoice response labelled; others raw). A DNS registration only shows the participant is reachable on Peppol, not that the company is verified. If the SMP cannot be read the DNS answer is still returned with smp_error. Bad IDs are a 422 and a DNS outage a 503 (neither charged). Typically 0.2-2 s. Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/peppol-participant-lookup-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
peppol_lookup accepts 2 parameters: scheme, participant. Required: participant. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for peppol_lookup: 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 Tanod. Nothing to install.
peppol_lookup is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the peppol_lookup 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 peppol_lookup. 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.
peppol_lookup is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue