lock_adom_workspace

A write tool on the Fortimanager MCP server.

SERVERFortimanager SOURCEjmpijll/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/jmpijll-fortimanager-mcp/lock-adom-workspace.md

WHAT IT DOES

What lock_adom_workspace does on Fortimanager

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

RISK

Why lock_adom_workspace is rated Medium

The name suggests locking an ADOM (Administrative Domain) workspace in FortiManager, which is a Write-type operation that modifies workspace state (acquiring a lock to prevent concurrent edits). This is reversible (locks can be unlocked). Confidence is low due to the empty description.

From the tool's definition Tool name: lock_adom_workspace; description is empty.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

lock_adom_workspace Rate-limited

lock_adom_workspace 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_workspace": {
      "limits": [
        {
          "counter": "lock_adom_workspace_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, apply this rule, and every lock_adom_workspace call is checked against it from then on.

FAQ

Questions about lock_adom_workspace

What does the lock_adom_workspace tool do? +

lock_adom_workspace is a write tool on the Fortimanager MCP server. It is categorised as a Write tool in the Fortimanager 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_workspace? +

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

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

Can I rate-limit lock_adom_workspace? +

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

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

lock_adom_workspace 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 →

Across the catalogue

The MCP Attack Database →

Guides

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