lock_adom

A write tool on the FortiManager MCP server.

SERVERFortiManager MCP Server SOURCErstierli/fortimanager-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rstierli-fortimanager-mcp/lock-adom.md

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.

RISK

Why lock_adom is rated Medium

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

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

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.

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

FAQ

Questions about lock_adom

What does the lock_adom tool do? +

lock_adom is a write tool on the FortiManager MCP Server MCP server. 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.

KEEP EXPLORING

More on FortiManager MCP Server, and thousands of servers like it.

This server

All 236 FortiManager MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →