Query relationships in the LSMS database. Find phone numbers by LRN, SPIDs by LRN or phone number, or LRNs by SPID or phone number. Queries live NPAC porting data (not static LERG reference data).
AI agents call lrn_relationship_query 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.
This tool retrieves telecom routing and porting data without modifying, deleting, or executing commands. It is a lookup/query operation that returns information about phone number relationships and service provider identifiers. No side effects beyond retrieving data are described. The blast radius of misuse is limited to potential exposure of telecom metadata, which is read-only in nature.
From the tool's definition Query relationships in the LSMS database. Find phone numbers by LRN, SPIDs by LRN or phone number, or LRNs by SPID or phone number. Queries live NPAC porting data (not static LERG reference data).
Attacks that exploit this kind of access
Query relationships in the LSMS database. Find phone numbers by LRN, SPIDs by LRN or phone number, or LRNs by SPID or phone number. Queries live NPAC porting data (not static LERG reference data). It is categorised as a Read tool in the Telique MCP MCP Server, which means it retrieves data without modifying state.
Register the Telique MCP server in PolicyLayer and add a rule for lrn_relationship_query: 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.
lrn_relationship_query 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 lrn_relationship_query 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 lrn_relationship_query. 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.
lrn_relationship_query 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.
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 →