clear_database_cache
A destructive tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/clear-database-cache.md
What clear_database_cache does on Fortimanager
AI agents call clear_database_cache to permanently remove resources in Fortimanager, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clear_database_cache is rated Critical
The name suggests clearing/purging a database cache, which is typically a destructive and irreversible operation. However, the empty description lowers confidence — 'clear cache' could be a non-destructive flush operation that regenerates automatically. Given the FortiManager context (network security management platform) and the naming pattern, this is more likely a destructive cache purge.
From the tool's definition Tool name 'clear_database_cache' implies irreversible removal of cached database data. Description is empty, providing no additional context.
Attacks that exploit this kind of access
The rule that runs clear_database_cache 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 clear_database_cache, this is the rule to start with:
clear_database_cache is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every clear_database_cache call is checked against it from then on.
Questions about clear_database_cache
clear_database_cache is a destructive tool on the Fortimanager MCP server. It is categorised as a Destructive tool in the Fortimanager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fortimanager MCP server in PolicyLayer and add a rule for clear_database_cache: 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.
clear_database_cache is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_database_cache 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 clear_database_cache. 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.
clear_database_cache 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.
Across the catalogue