delete_meta_field

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/delete-meta-field.md

WHAT IT DOES

What delete_meta_field does on Fortimanager

AI agents call delete_meta_field 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.

RISK

Why delete_meta_field is rated Critical

The 'delete' prefix strongly suggests this tool permanently removes metadata fields from FortiManager objects. Without description details, we cannot determine the scope, but the destructive verb places this in the Destructive category.

From the tool's definition Tool name 'delete_meta_field' explicitly uses 'delete' verb, indicating irreversible removal of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_meta_field 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_meta_field, this is the rule to start with:

delete_meta_field Hidden

delete_meta_field is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_meta_field"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every delete_meta_field call is checked against it from then on.

FAQ

Questions about delete_meta_field

What does the delete_meta_field tool do? +

delete_meta_field 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 delete_meta_field? +

Register the Fortimanager MCP server in PolicyLayer and add a rule for delete_meta_field: 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 delete_meta_field? +

delete_meta_field 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 delete_meta_field? +

Yes. Add a rate_limit block to the delete_meta_field 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 delete_meta_field completely? +

Set action: deny in the PolicyLayer policy for delete_meta_field. 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 delete_meta_field? +

delete_meta_field 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.

KEEP EXPLORING

More on Fortimanager, and thousands of servers like it.

This server

All 584 Fortimanager tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →