Query any LERG table by field values. Common queries: carrier by OCN (lerg_1, fields: ocn_num,ocn_name,ocn_state), NPA-NXX info (lerg_6, fields: npa,nxx,loc_name,ocn,switch,lata), switch details (lerg_7, fields: switch,ocn,aocn), LRN registry (lerg_12, fields: lrn,lata,switch,ocn). Filter format:...
AI agents call lerg_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 and filters telecom routing information from pre-existing LERG databases. It is a read-only query operation with no side effects, data modification, code execution, or destructive capability. The severity is low because misuse would only expose routing metadata without enabling financial transactions or system compromise.
From the tool's definition Tool performs queries on telecom routing data tables (LERG) with filtering by field values. Description uses action verbs 'Query' and examples show retrieval operations: 'carrier by OCN', 'NPA-NXX info', 'switch details', 'LRN registry'.
Attacks that exploit this kind of access
Query any LERG table by field values. Common queries: carrier by OCN (lerg_1, fields: ocn_num,ocn_name,ocn_state), NPA-NXX info (lerg_6, fields: npa,nxx,loc_name,ocn,switch,lata), switch details (lerg_7, fields: switch,ocn,aocn), LRN registry (lerg_12, fields: lrn,lata,switch,ocn). Filter format: field=value, multiple filters joined with & (e.g. npa=303&nxx=629). 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 lerg_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.
lerg_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 lerg_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 lerg_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.
lerg_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 →