ips_sensor_get

A read tool on the FortiOS 7 6 X MCP server.

SERVERFortiOS 7 6 X MCP Server SOURCEpaoloamato2/fortinet-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/paoloamato2-fortinet-mcp-server/ips-sensor-get.md

WHAT IT DOES

What ips_sensor_get does on FortiOS 7 6 X MCP Server

AI agents call ips_sensor_get to retrieve information from FortiOS 7 6 X MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ips_sensor_get is rated Low

This tool retrieves IPS (Intrusion Prevention System) sensor configuration data from FortiOS without modifying state. No destructive, financial, or execution capabilities are implied. While the description is empty, the naming pattern and server context provide high confidence this is a simple read operation.

From the tool's definition Tool name 'ips_sensor_get' follows REST GET convention, indicating data retrieval. The '_get' suffix and context within a FortiOS configuration server (sibling tools are all read-only: *_get, *_list operations) strongly suggest querying IPS sensor…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ips_sensor_get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FortiOS 7 6 X MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ips_sensor_get, this is the rule to start with:

ips_sensor_get Allowed

ips_sensor_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ips_sensor_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FortiOS 7 6 X MCP Server, apply this rule, and every ips_sensor_get call is checked against it from then on.

FAQ

Questions about ips_sensor_get

What does the ips_sensor_get tool do? +

ips_sensor_get is a read tool on the FortiOS 7 6 X MCP Server MCP server. It is categorised as a Read tool in the FortiOS 7 6 X MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ips_sensor_get? +

Register the FortiOS 7 6 X MCP Server MCP server in PolicyLayer and add a rule for ips_sensor_get: 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 FortiOS 7 6 X MCP Server. Nothing to install.

What risk level is ips_sensor_get? +

ips_sensor_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ips_sensor_get? +

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

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

ips_sensor_get is provided by the FortiOS 7 6 X MCP Server MCP server (paoloamato2/fortinet-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FortiOS 7 6 X MCP Server, and thousands of servers like it.

This server

All 240 FortiOS 7 6 X MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →