get_auto_update_configuration
Get automatic update status and schedule.
This record as markdown: /tools/jmpijll-fortimanager-mcp/get-auto-update-configuration.md
What get_auto_update_configuration does on Fortimanager
AI agents call get_auto_update_configuration 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_auto_update_configuration is rated Low
This tool queries and retrieves configuration data about automatic update settings without performing any actions, modifications, or destructive operations. It is purely informational—getting status and schedule information fits the 'Read' category as it retrieves data with no side effects.
From the tool's definition Tool name 'get_auto_update_configuration' and description 'Get automatic update status and schedule' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_auto_update_configuration 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_auto_update_configuration, this is the rule to start with:
get_auto_update_configuration 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_auto_update_configuration call is checked against it from then on.
Questions about get_auto_update_configuration
Get automatic update status and schedule. 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_auto_update_configuration: 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_auto_update_configuration 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_auto_update_configuration 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_auto_update_configuration. 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_auto_update_configuration 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