get_dlp_sensor
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-dlp-sensor.md
What get_dlp_sensor does on Fortimanager
AI agents call get_dlp_sensor to retrieve information from Fortimanager without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dlp_sensor is rated Low
Although the description is empty, reducing confidence slightly, the tool name strongly suggests querying or retrieving DLP sensor data from FortiManager rather than modifying, executing, or deleting. DLP sensors contain security policies and configuration data. Unauthorized access to DLP sensor configurations could expose sensitive security policies and filtering rules, justifying medium severity.
From the tool's definition Tool name 'get_dlp_sensor' indicates data retrieval of DLP (Data Loss Prevention) sensor configurations. The 'get_' prefix is characteristic of Read operations.
Attacks that exploit this kind of access
The rule that runs get_dlp_sensor safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fortimanager, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dlp_sensor, this is the rule to start with:
get_dlp_sensor 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 Fortimanager, apply this rule, and every get_dlp_sensor call is checked against it from then on.
Questions about get_dlp_sensor
get_dlp_sensor is a read tool on the Fortimanager MCP server. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.
Register the Fortimanager MCP server in PolicyLayer and add a rule for get_dlp_sensor: 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 Fortimanager. Nothing to install.
get_dlp_sensor 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_dlp_sensor 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_dlp_sensor. 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_dlp_sensor is provided by the Fortimanager MCP server (jmpijll/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fortimanager, and thousands of servers like it.
This server
Across the catalogue