lookup_tn

Composite phone number lookup across multiple Telique services. Dips LRN, CNAM, DNO, and LERG (NPA-NXX from lerg_6) in parallel and returns a consolidated view. Use this for a quick, comprehensive profile of any phone number.

Server Telique MCP ringer/telique-mcp
Category Read
Risk class Low
Parameters 00 required

What lookup_tn does on Telique MCP

AI agents call lookup_tn to retrieve information from Telique MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why lookup_tn needs a policy

This is a read-only query tool that retrieves telecom routing and caller identification data from multiple sources. While the data accessed (LRN, CNAM, DNO routing information) could be sensitive and enable phone enumeration or reconnaissance attacks, the tool itself performs only data retrieval without side effects.

From the tool's definition Tool description states it 'Dips LRN, CNAM, DNO, and LERG' and 'returns a consolidated view' of phone number data. The verb 'lookup' and 'Composite phone number lookup' indicate data retrieval with no modification or deletion.

Questions about lookup_tn

What does the lookup_tn tool do? +

Composite phone number lookup across multiple Telique services. Dips LRN, CNAM, DNO, and LERG (NPA-NXX from lerg_6) in parallel and returns a consolidated view. Use this for a quick, comprehensive profile of any phone number. It is categorised as a Read tool in the Telique MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_tn? +

Register the Telique MCP server in PolicyLayer and add a rule for lookup_tn: 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 Telique MCP. Nothing to install.

What risk level is lookup_tn? +

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

Can I rate-limit lookup_tn? +

Yes. Add a rate_limit block to the lookup_tn 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 lookup_tn completely? +

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

lookup_tn is provided by the Telique MCP server (ringer/telique-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.