Get automatic update status and schedule.
AI agents call get_auto_update_configuration to retrieve information from Fortimanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration data about automatic updates without modifying, executing, or deleting anything. It is a passive information retrieval operation with no side effects, making it a Read category tool with low severity since disclosure of update schedules poses minimal risk.
From the tool's definition The tool name is 'get_auto_update_configuration' and the description states it 'Get automatic update status and schedule.' The verb 'get' and the explicit retrieval intent indicates a read-only query operation.
Documented attack patterns abuse exactly the kind of access get_auto_update_configuration gives an agent:
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_auto_update_configuration:
{
"version": "1",
"default": "deny",
"tools": {
"get_auto_update_configuration": {}
}
}get_auto_update_configuration is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.