clear_database_cache

A destructive tool on the Fortimanager MCP server.

SERVERFortimanager SOURCEjmpijll/fortimanager-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about clear_database_cache

What does the clear_database_cache tool do? +

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.

How do I enforce a policy on clear_database_cache? +

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.

What risk level is clear_database_cache? +

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.

Can I rate-limit clear_database_cache? +

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.

How do I block clear_database_cache completely? +

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.

What MCP server provides clear_database_cache? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Fortimanager's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.