get_dem_locations
Get available monitoring locations for a DEM application.
This record as markdown: /tools/gjenkins20-unofficial-fortimonitor-mcp-server/get-dem-locations.md
What get_dem_locations does on Unofficial FortiMonitor MCP Server
AI agents call get_dem_locations to retrieve information from Unofficial FortiMonitor MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dem_locations is rated Low
This tool retrieves configuration or status data about DEM (Digital Experience Monitoring) application locations. It performs a simple data query with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an agent could enumerate monitoring locations but cannot alter infrastructure or trigger actions.
From the tool's definition Tool name 'get_dem_locations' and description 'Get available monitoring locations for a DEM application' indicate a query/retrieval operation with no modification or execution of external commands.
Attacks that exploit this kind of access
The rule that runs get_dem_locations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unofficial FortiMonitor MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dem_locations, this is the rule to start with:
get_dem_locations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Unofficial FortiMonitor MCP Server, apply this rule, and every get_dem_locations call is checked against it from then on.
Questions about get_dem_locations
Get available monitoring locations for a DEM application. It is categorised as a Read tool in the Unofficial FortiMonitor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unofficial FortiMonitor MCP Server MCP server in PolicyLayer and add a rule for get_dem_locations: 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 Unofficial FortiMonitor MCP Server. Nothing to install.
get_dem_locations 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 get_dem_locations 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 get_dem_locations. 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.
get_dem_locations is provided by the Unofficial FortiMonitor MCP Server MCP server (gjenkins20/unofficial-fortimonitor-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unofficial FortiMonitor MCP Server, and thousands of servers like it.
Across the catalogue