delete_object_metadata
A destructive tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/delete-object-metadata.md
What delete_object_metadata does on Fortimanager
AI agents call delete_object_metadata 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 delete_object_metadata is rated Critical
The 'delete' operation is classified as Destructive because it removes data irreversibly. Although the description is empty (lowering confidence slightly), the explicit 'delete' in the name combined with the context of a FortiManager administration tool suggests this deletes configuration or metadata objects that cannot be easily restored.
From the tool's definition Tool name 'delete_object_metadata' contains the verb 'delete', which indicates irreversible removal of data. No description provided to confirm scope or reversibility.
Attacks that exploit this kind of access
The rule that runs delete_object_metadata 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 delete_object_metadata, this is the rule to start with:
delete_object_metadata 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 delete_object_metadata call is checked against it from then on.
Questions about delete_object_metadata
delete_object_metadata 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 delete_object_metadata: 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.
delete_object_metadata 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 delete_object_metadata 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 delete_object_metadata. 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.
delete_object_metadata 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