This record as markdown: /tools/jmpijll-fortimanager-mcp/unlock-device-workspace.md
What unlock_device_workspace does on Fortimanager
AI agents use unlock_device_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_device_workspace is rated Medium
This tool modifies device state by unlocking it, which is a reversible write operation. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), and does not involve financial transactions (not Financial). The severity is medium because unlocking a device could allow unauthorized access or modification if misused by an AI agent, but the operation itself is reversible.
From the tool's definition Tool name 'unlock_device_workspace' and description 'Unlock a device' indicate a state change operation that modifies device lock status.
Attacks that exploit this kind of access
The rule that runs unlock_device_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_device_workspace, this is the rule to start with:
unlock_device_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_device_workspace call is checked against it from then on.
Questions about unlock_device_workspace
Unlock a device. 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_device_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_device_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_device_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_device_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_device_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