get_device_interface_config
A read tool on the FortiManager MCP server.
This record as markdown: /tools/rstierli-fortimanager-mcp/get-device-interface-config.md
What get_device_interface_config does on FortiManager MCP Server
AI agents call get_device_interface_config to retrieve information from FortiManager MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_device_interface_config is rated Low
The 'get_' prefix is a strong signal for read-only operations. Combined with the FortiManager server's configuration management context, this tool likely retrieves device interface configuration details for querying or auditing purposes. No destructive, write, or execute capabilities are implied by the name. Confidence is slightly reduced due to empty description, but the naming convention is reliable.
From the tool's definition Tool name 'get_device_interface_config' uses 'get' prefix, indicating data retrieval. Description is empty, but context from sibling tools (add_*, assign_*, clone_*) and server purpose (centralized firewall policy management) suggests this retrieves interface…
Attacks that exploit this kind of access
The rule that runs get_device_interface_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FortiManager MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_device_interface_config, this is the rule to start with:
get_device_interface_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FortiManager MCP Server, apply this rule, and every get_device_interface_config call is checked against it from then on.
Questions about get_device_interface_config
get_device_interface_config is a read tool on the FortiManager MCP Server MCP server. It is categorised as a Read tool in the FortiManager MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for get_device_interface_config: 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 MCP Server. Nothing to install.
get_device_interface_config 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 get_device_interface_config 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 get_device_interface_config. 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.
get_device_interface_config is provided by the FortiManager MCP Server MCP server (rstierli/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FortiManager MCP Server, and thousands of servers like it.
This server
Across the catalogue