get_ipsec_tunnel_status
A read tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-ipsec-tunnel-status.md
What get_ipsec_tunnel_status does on Fortimanager
AI agents call get_ipsec_tunnel_status 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_ipsec_tunnel_status is rated Low
This tool retrieves information about IPsec tunnel status without modifying, deleting, or executing operations. While the description is empty, the naming convention clearly indicates a read operation with minimal blast radius if misused by an agent—it would only return status information. Confidence is slightly reduced due to the absent description, but the tool name provides sufficient clarity for classification.
From the tool's definition Tool name 'get_ipsec_tunnel_status' indicates a retrieval operation querying the status of IPsec tunnels. No parameters are specified that would permit modification or deletion. The verb 'get' and noun 'status' are consistent with read-only queries.
Attacks that exploit this kind of access
The rule that runs get_ipsec_tunnel_status 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_ipsec_tunnel_status, this is the rule to start with:
get_ipsec_tunnel_status 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_ipsec_tunnel_status call is checked against it from then on.
Questions about get_ipsec_tunnel_status
get_ipsec_tunnel_status 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_ipsec_tunnel_status: 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_ipsec_tunnel_status 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_ipsec_tunnel_status 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_ipsec_tunnel_status. 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_ipsec_tunnel_status 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