lock_adom · FortiManager MCP Server MCP: Risk & Policy

WHAT IT DOES

What lock_adom does on FortiManager MCP Server

AI agents use lock_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 lock_adom needs a policy

In FortiManager, locking an ADOM (Administrative Domain) is a standard workflow step before making configuration changes. It restricts other administrators from modifying the ADOM simultaneously. This is a reversible write/state-change operation (can be unlocked), not destructive.

From the tool's definition Tool name: lock_adom; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lock_adom Rate-limited

lock_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": {
    "lock_adom": {
      "limits": [
        {
          "counter": "lock_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 lock_adom

What does the lock_adom tool do? +

lock_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 lock_adom? +

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

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

Can I rate-limit lock_adom? +

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

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

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