create_eventsource

Create an EventSource via REST API from a full definition dict

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/create-eventsource.md

WHAT IT DOES

What create_eventsource does on Logicmonitor

AI agents use create_eventsource 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 create_eventsource is rated Medium

An AI agent can call create_eventsource 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 create_eventsource 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 create_eventsource, this is the rule to start with:

create_eventsource Rate-limited

create_eventsource 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": {
    "create_eventsource": {
      "limits": [
        {
          "counter": "create_eventsource_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 create_eventsource call is checked against it from then on.

FAQ

Questions about create_eventsource

What does the create_eventsource tool do? +

Create an EventSource via REST API from a full definition dict. 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 create_eventsource? +

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

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

Can I rate-limit create_eventsource? +

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

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

create_eventsource 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

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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