List all 27 LERG tables or get metadata/schema for a specific table. LERG is static telecom reference data. Key tables: lerg_1 (OCN/carrier directory), lerg_6 (NPA-NXX block assignments with switch, LATA, rate center), lerg_7 (switch details), lerg_7_sha (switch homing arrangements/tandems), lerg...
AI agents call lerg_table_info 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 only retrieves and queries static reference data about telecom routing infrastructure. It performs no modifications, deletions, code execution, or financial transactions. The 'lerg_table_info' operation is read-only schema introspection. Even though the underlying data is telecom-related, the tool itself has no side effects and cannot alter, destroy, or move anything.
From the tool's definition Tool description explicitly states 'List all 27 LERG tables or get metadata/schema for a specific table' and 'LERG is static telecom reference data.' The operations are purely informational: listing table names and retrieving metadata/schema information.
Attacks that exploit this kind of access
List all 27 LERG tables or get metadata/schema for a specific table. LERG is static telecom reference data. Key tables: lerg_1 (OCN/carrier directory), lerg_6 (NPA-NXX block assignments with switch, LATA, rate center), lerg_7 (switch details), lerg_7_sha (switch homing arrangements/tandems), lerg_12 (LRN registry). 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_table_info: 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_table_info 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_table_info 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_table_info. 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_table_info 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 →