get_device_profile

Get detailed information about a specific device profile.

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/get-device-profile.md

WHAT IT DOES

What get_device_profile does on Fortimanager

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

This tool retrieves or queries information about a device profile without modifying, deleting, or executing any operations. It is a straightforward read operation that returns data, fitting the Read category. The severity is low as accessing profile information alone poses minimal risk to system integrity.

From the tool's definition Tool name 'get_device_profile' and description 'Get detailed information about a specific device profile' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_device_profile Allowed

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

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

FAQ

Questions about get_device_profile

What does the get_device_profile tool do? +

Get detailed information about a specific device profile. 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_profile? +

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

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

Can I rate-limit get_device_profile? +

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

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

get_device_profile 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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