Low Risk

get_install_targets

Get list of devices available for policy installation.

How to control get_install_targets ↓

What get_install_targets does on Fortimanager

AI agents call get_install_targets to retrieve information from Fortimanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_install_targets needs a policy

This tool retrieves a list of devices without modifying, deleting, or executing any operations. It is purely informational and presents minimal risk if misused by an AI agent, as it only returns data about available installation targets.

From the tool's definition Tool name 'get_install_targets' and description 'Get list of devices available for policy installation' indicate a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_install_targets gives an agent:

How to control get_install_targets

PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for get_install_targets:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_install_targets": {}
  }
}

get_install_targets is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Fortimanager — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_install_targets

What does the get_install_targets tool do? +

Get list of devices available for policy installation. 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 get_install_targets? +

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

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

Can I rate-limit get_install_targets? +

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

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

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

Enforce policy on every Fortimanager tool call.

Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.