get_device_install_history

THE RISK

Low Risk

Why get_device_install_history needs a policy

This tool queries historical data about device installations. It performs a read-only retrieval operation without modifying, deleting, or executing any actions. The low severity reflects minimal blast radius if misused—an agent could only expose historical information, not alter system state.

From the tool's definition Tool name 'get_device_install_history' uses the verb 'get', and the description states it retrieves 'installation history for a specific device'. This is a query operation with no side effects.

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

POLICY

How to control get_device_install_history

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_device_install_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_device_install_history": {}
  }
}

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

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Fortimanager tools

Destructive bulk_delete_security_profile_entries bulk_delete_security_profile_entries Destructive clear_database_cache clear_database_cache Destructive delete_adom_revision delete_adom_revision Destructive delete_central_dnat_policy Delete a central DNAT policy. Destructive delete_central_snat_policy Delete a central SNAT policy. Destructive delete_certificate_template delete_certificate_template Destructive delete_cli_script delete_cli_script Destructive delete_cli_template Delete a CLI template.

All 584 Fortimanager tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_device_install_history

What does the get_device_install_history tool do? +

Get installation history for a specific 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 get_device_install_history? +

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

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

Can I rate-limit get_device_install_history? +

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

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

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

CHECK YOUR STACK →