New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

validate_identifier

utilpeek: check the format and check digits of an identifier. For a VIN's vehicle use decode_vin; for phone numbers use parse_phone_number. Returns valid, reason (invalid_checksum, invalid_length, invalid_format, ... when not valid), compact, formatted and a kind-specific detail (an IBAN's countr...

SERVERTanod SOURCEhttps://tanod.dev/mcp
Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/validate-identifier.md

What validate_identifier does on Tanod

AI agents call validate_identifier 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.

ParameterTypeRequiredDescription
kind string Yes Identifier kind: iban, bic, vat (EU, format only, no VIES), isbn, issn, ean, isin, lei, imo, luhn (generic mod-10), or a national format (au_abn, br_cnpj, br_cp
value string Yes The identifier (1-64 printable ASCII characters).

Parameters from the server's own tool schema.

Why validate_identifier is rated Low

Even though validate_identifier 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.

Questions about validate_identifier

What does the validate_identifier tool do? +

utilpeek: check the format and check digits of an identifier. For a VIN's vehicle use decode_vin; for phone numbers use parse_phone_number. Returns valid, reason (invalid_checksum, invalid_length, invalid_format, ... when not valid), compact, formatted and a kind-specific detail (an IBAN's country and bank code, an ISBN's ISBN-10/13 forms, ...). An invalid identifier is a normal answer (charged); a malformed request is a 422 (not charged). Checks format and check digits only, offline (python-stdnum): a valid result does not mean the identifier exists or is registered (no registry, bank or VIES call). Payment card numbers are not accepted, not even under luhn. The submitted value is processed in memory only, never logged or stored. Typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/iban-validation-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.

What parameters does validate_identifier accept? +

validate_identifier accepts 2 parameters: kind, value. Required: kind, value. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on validate_identifier? +

Register the Tanod MCP server in PolicyLayer and add a rule for validate_identifier: 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.

What risk level is validate_identifier? +

validate_identifier is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit validate_identifier? +

Yes. Add a rate_limit block to the validate_identifier 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.

How do I block validate_identifier completely? +

Set action: deny in the PolicyLayer policy for validate_identifier. 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.

What MCP server provides validate_identifier? +

validate_identifier 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tanod's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.