get_admin_config
Get administrative settings including session timeout and lockout policy.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-admin-config.md
What get_admin_config does on Fortimanager
AI agents call get_admin_config 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.
Why get_admin_config is rated Low
The tool retrieves or queries administrative configuration data (session timeout, lockout policy) without creating, modifying, deleting, or executing any operations. This is a straightforward read operation with minimal security impact on its own, though the sensitivity of the data retrieved (administrative settings) prevents it from being classified as trivial.
From the tool's definition Tool name 'get_admin_config' and description 'Get administrative settings including session timeout and lockout policy' indicate a retrieval operation with no modification or execution of external operations.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_admin_config 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_admin_config, this is the rule to start with:
get_admin_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, apply this rule, and every get_admin_config call is checked against it from then on.
Questions about get_admin_config
Get administrative settings including session timeout and lockout policy. 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 get_admin_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. Nothing to install.
get_admin_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_admin_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_admin_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_admin_config 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.
More on Fortimanager, and thousands of servers like it.
This server
Across the catalogue