delete_local_in_policy6

A destructive tool on the FortiManager MCP server.

SERVERFortiManager MCP Server SOURCErstierli/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/rstierli-fortimanager-mcp/delete-local-in-policy6.md

WHAT IT DOES

What delete_local_in_policy6 does on FortiManager MCP Server

AI agents call delete_local_in_policy6 to permanently remove resources in FortiManager MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_local_in_policy6 is rated Critical

Deletes firewall policies irreversibly, affecting network security posture and cannot be undone without restoration procedures.

From the tool's definition delete_local_in_policy6; FortiManager firewall policy management

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_local_in_policy6 safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FortiManager MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_local_in_policy6, this is the rule to start with:

delete_local_in_policy6 Hidden

delete_local_in_policy6 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_local_in_policy6"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_local_in_policy6

What does the delete_local_in_policy6 tool do? +

delete_local_in_policy6 is a destructive tool on the FortiManager MCP Server MCP server. It is categorised as a Destructive tool in the FortiManager MCP Server 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_local_in_policy6? +

Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for delete_local_in_policy6: 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 MCP Server. Nothing to install.

What risk level is delete_local_in_policy6? +

delete_local_in_policy6 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_local_in_policy6? +

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

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

delete_local_in_policy6 is provided by the FortiManager MCP Server MCP server (rstierli/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 MCP Server, and thousands of servers like it.

This server

All 236 FortiManager MCP Server 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 →