import_propertysource
Import a PropertySource from LM Exchange JSON format via multipart
This record as markdown: /tools/io-github-ryanmat-logicmonitor/import-propertysource.md
What import_propertysource does on Logicmonitor
AI agents use import_propertysource 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.
Why import_propertysource is rated Medium
An AI agent can call import_propertysource 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
The rule that runs import_propertysource 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 import_propertysource, this is the rule to start with:
import_propertysource 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Logicmonitor, apply this rule, and every import_propertysource call is checked against it from then on.
Questions about import_propertysource
Import a PropertySource from LM Exchange JSON format via multipart. 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.
Register the Logicmonitor MCP server in PolicyLayer and add a rule for import_propertysource: 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.
import_propertysource is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_propertysource 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 import_propertysource. 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.
import_propertysource 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.
More on Logicmonitor, and thousands of servers like it.
This server
Across the catalogue