push_metrics

Push custom metrics into LogicMonitor (requires LMv1 auth)

SERVERLogicmonitor SOURCEpypi:lm-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What push_metrics does on Logicmonitor

AI agents use push_metrics to create or update resources in Logicmonitor, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Logicmonitor environment.

RISK

Why push_metrics is rated Medium

An AI agent can call push_metrics faster than any human can review: one bad instruction and it creates or modifies resources in Logicmonitor by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs push_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 push_metrics, this is the rule to start with:

push_metrics Rate-limited

push_metrics stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "push_metrics": {
      "limits": [
        {
          "counter": "push_metrics_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about push_metrics

What does the push_metrics tool do? +

Push custom metrics into LogicMonitor (requires LMv1 auth). It is categorised as a Write tool in the Logicmonitor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on push_metrics? +

Register the Logicmonitor MCP server in PolicyLayer and add a rule for push_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 push_metrics? +

push_metrics is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit push_metrics? +

Yes. Add a rate_limit block to the push_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 push_metrics completely? +

Set action: deny in the PolicyLayer policy for push_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 push_metrics? +

push_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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →