Execute a complex LERG query with JOINs across multiple tables. Supports filter operators: eq, ne, gt, gte, lt, lte, like, in, isnull, isnotnull. Use this when you need to combine data from different LERG tables, such as joining NPA-NXX (lerg_6) with carrier info (lerg_1) via OCN.
AI agents invoke lerg_complex_query to trigger actions in Telique MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes complex SQL-like queries with JOINs and filter operators against telecom routing database tables. While it appears to be read-only in nature (querying LERG data), the 'execute' framing and support for complex query construction with multiple operators indicates it runs arbitrary structured queries rather than a simple lookup.
From the tool's definition "Execute a complex LERG query with JOINs across multiple tables" and "Supports filter operators: eq, ne, gt, gte, lt, lte, like, in, isnull, isnotnull"
Attacks that exploit this kind of access
Execute a complex LERG query with JOINs across multiple tables. Supports filter operators: eq, ne, gt, gte, lt, lte, like, in, isnull, isnotnull. Use this when you need to combine data from different LERG tables, such as joining NPA-NXX (lerg_6) with carrier info (lerg_1) via OCN. It is categorised as a Execute tool in the Telique MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Telique MCP server in PolicyLayer and add a rule for lerg_complex_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_complex_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lerg_complex_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_complex_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_complex_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.
lerg_complex_query is one line of Telique's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →