unlock_adom · FortiManager MCP Server MCP: Risk & Policy

WHAT IT DOES

What unlock_adom does on FortiManager MCP Server

AI agents use unlock_adom to create or update resources in FortiManager MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FortiManager MCP Server environment.

WHY IT NEEDS A POLICY

Why unlock_adom needs a policy

The tool performs a state modification (unlocking an adom/administrative domain) rather than deletion, but affects access control and object state in a centralized firewall management system. Without an explicit description, confidence is moderate. This is categorized as Write rather than Execute because it modifies object state directly rather than executing arbitrary operations.

From the tool's definition Tool name 'unlock_adom' suggests unlocking an Admin Domain object in FortiManager. The 'unlock' action indicates modification of state/access control on a managed object, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

unlock_adom Rate-limited

unlock_adom stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "unlock_adom": {
      "limits": [
        {
          "counter": "unlock_adom_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches FortiManager MCP Server, so you can run agents against it safely.

FAQ

Questions about unlock_adom

What does the unlock_adom tool do? +

unlock_adom. It is categorised as a Write tool in the FortiManager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on unlock_adom? +

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

unlock_adom is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit unlock_adom? +

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

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

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