list_scheduled_installs

A read tool on the Fortimanager MCP server.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp

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/jmpijll-fortimanager-mcp/list-scheduled-installs.md

WHAT IT DOES

What list_scheduled_installs does on Fortimanager

AI agents call list_scheduled_installs 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.

RISK

Why list_scheduled_installs is rated Low

The 'list' verb strongly suggests this tool retrieves or queries scheduled installation data from FortiManager without modifying anything. The empty description prevents higher confidence, but the naming pattern is consistent with Read operations (no side effects expected). Context from sibling tools (add_*, abort_*) further suggests this is a query/retrieval function.

From the tool's definition Tool name 'list_scheduled_installs' uses the verb 'list', which indicates data retrieval. Description is empty, limiting confidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_scheduled_installs 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 list_scheduled_installs, this is the rule to start with:

list_scheduled_installs Allowed

list_scheduled_installs 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": {
    "list_scheduled_installs": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every list_scheduled_installs call is checked against it from then on.

FAQ

Questions about list_scheduled_installs

What does the list_scheduled_installs tool do? +

list_scheduled_installs 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.

How do I enforce a policy on list_scheduled_installs? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for list_scheduled_installs: 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.

What risk level is list_scheduled_installs? +

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

Can I rate-limit list_scheduled_installs? +

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

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

list_scheduled_installs 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.

KEEP EXPLORING

More on Fortimanager, and thousands of servers like it.

This server

All 584 Fortimanager tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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