nlq_to_data
AI agents call nlq_to_data to retrieve information from Lumenore Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite empty tool description, the naming pattern ('nlq_to_data'), sibling context (all get_* analytics operations), and server design (zero persistent storage, read-only insights) strongly indicate this tool retrieves or queries data without side effects. No evidence of write, execute, delete, or financial capabilities.
From the tool's definition Tool name is 'nlq_to_data' (natural language query to data), placed among sibling tools that are all read-only analytics functions (get_trend_data, get_prediction_data, get_outlier_data, get_correlation_data, etc.).
Attacks that exploit this kind of access
nlq_to_data. It is categorised as a Read tool in the Lumenore Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lumenore Analytics MCP Server MCP server in PolicyLayer and add a rule for nlq_to_data: 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 Lumenore Analytics MCP Server. Nothing to install.
nlq_to_data 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 nlq_to_data 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 nlq_to_data. 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.
nlq_to_data is provided by the Lumenore Analytics MCP Server MCP server (lumenore-platform/lumenore-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 →