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.
Based on the tool name, 'lock_adom_workspace' likely locks an ADOM (Administrative Domain) workspace in FortiManager, which is a Write operation that modifies the state of the workspace. Locking is typically a reversible operation (it can be unlocked), so it falls under Write rather than Destructive. Severity is medium as locking a workspace could block other administrators from making changes.
From the tool's definition Tool name: lock_adom_workspace. Description is empty.
Documented attack patterns abuse exactly the kind of access lock_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 lock_adom_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"lock_adom_workspace": {
"limits": [
{
"counter": "lock_adom_workspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
lock_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 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.
lock_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 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.
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.
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.
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.