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.
Unlocking a workspace is a write operation that modifies FortiManager's collaborative editing locks. While reversible (can be re-locked), it affects system state and could allow unauthorized modifications to policy configurations if misused by an agent. The high severity reflects that FortiManager controls critical network security policies.
From the tool's definition Tool name 'unlock_adom_workspace' indicates modification of workspace lock state in FortiManager's Administrative Domain (ADOM). The 'unlock' operation modifies system state reversibly. Description is empty, reducing confidence slightly.
Documented attack patterns abuse exactly the kind of access unlock_adom_workspace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for unlock_adom_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"unlock_adom_workspace": {
"limits": [
{
"counter": "unlock_adom_workspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
unlock_adom_workspace. 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.
Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
584 Fortimanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.