query_otlp_metrics

[PREVIEW] Run a PromQL range query against native OTLP metrics.

SERVERLogicmonitor SOURCEpypi:lm-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ryanmat-logicmonitor/query-otlp-metrics.md

WHAT IT DOES

What query_otlp_metrics does on Logicmonitor

AI agents call query_otlp_metrics to retrieve information from Logicmonitor without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why query_otlp_metrics is rated Low

Even though query_otlp_metrics only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_otlp_metrics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Logicmonitor, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_otlp_metrics, this is the rule to start with:

query_otlp_metrics Allowed

query_otlp_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_otlp_metrics": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Logicmonitor, apply this rule, and every query_otlp_metrics call is checked against it from then on.

FAQ

Questions about query_otlp_metrics

What does the query_otlp_metrics tool do? +

[PREVIEW] Run a PromQL range query against native OTLP metrics. It is categorised as a Read tool in the Logicmonitor MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_otlp_metrics? +

Register the Logicmonitor MCP server in PolicyLayer and add a rule for query_otlp_metrics: 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 Logicmonitor. Nothing to install.

What risk level is query_otlp_metrics? +

query_otlp_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_otlp_metrics? +

Yes. Add a rate_limit block to the query_otlp_metrics 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.

How do I block query_otlp_metrics completely? +

Set action: deny in the PolicyLayer policy for query_otlp_metrics. 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.

What MCP server provides query_otlp_metrics? +

query_otlp_metrics is provided by the Logicmonitor MCP server (pypi:lm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Logicmonitor, and thousands of servers like it.

This server

All 306 Logicmonitor tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →