Verify that a package was successfully installed on a device.
AI agents call verify_package_installation 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.
This tool retrieves and checks the installation status of a package on a device. It performs no modifications, deletions, or side effects—it only reads and reports state information. This is a classic Read operation with minimal risk if misused by an AI agent, as it cannot change system configuration or data.
From the tool's definition The tool name 'verify_package_installation' and description 'Verify that a package was successfully installed on a device' indicate a query/status-check operation. The verb 'verify' denotes inspection or confirmation without modification.
Documented attack patterns abuse exactly the kind of access verify_package_installation gives an agent:
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 verify_package_installation:
{
"version": "1",
"default": "deny",
"tools": {
"verify_package_installation": {}
}
}verify_package_installation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
verify_package_installation 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 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.
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.
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.
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.