unlock_adom_workspace
A write tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/unlock-adom-workspace.md
What unlock_adom_workspace does on Fortimanager
AI agents use unlock_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.
Why unlock_adom_workspace is rated Medium
The tool modifies the lock status of an ADOM workspace, which is a reversible change to system state. This is a Write action rather than Destructive because unlocking is not irreversible and does not delete data. Severity is high because improper unlocking of security policy workspaces in FortiManager could allow unauthorized concurrent modifications to critical firewall configurations.
From the tool's definition Tool name 'unlock_adom_workspace' indicates modification of workspace lock state. ADOM (Administrative Domain) workspace locks are management controls in FortiManager. Unlocking reverses a lock state, making it a state modification action.
Attacks that exploit this kind of access
The rule that runs unlock_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 unlock_adom_workspace, this is the rule to start with:
unlock_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every unlock_adom_workspace call is checked against it from then on.
Questions about unlock_adom_workspace
unlock_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.
Register the Fortimanager MCP server in PolicyLayer and add a rule for unlock_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.
unlock_adom_workspace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unlock_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.
Set action: deny in the PolicyLayer policy for unlock_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.
unlock_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.
More on Fortimanager, and thousands of servers like it.
This server
Across the catalogue