verify_package_installation

Verify that a package was successfully installed on a device.

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/verify-package-installation.md

WHAT IT DOES

What verify_package_installation does on Fortimanager

AI agents call verify_package_installation 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 verify_package_installation is rated Low

This tool retrieves installation status information from a device without creating, modifying, deleting, or executing any operations. It is a read-only verification query, making it a Read category risk with low severity since misuse would only expose status data rather than cause system changes.

From the tool's definition Tool name 'verify_package_installation' and description 'Verify that a package was successfully installed on a device' indicate a query/status-check operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

verify_package_installation Allowed

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

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 verify_package_installation call is checked against it from then on.

FAQ

Questions about verify_package_installation

What does the verify_package_installation tool do? +

Verify that a package was successfully installed on a device. 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 verify_package_installation? +

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

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

Can I rate-limit verify_package_installation? +

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

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

verify_package_installation 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

The MCP Attack Database →

Guides

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