AI agents use lock_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.
Based on the tool name alone, 'lock_device_workspace' most likely locks a device workspace in FortiManager, preventing concurrent edits — a reversible write-level action. However, with no description available, confidence is low. Locking is typically a Write operation (not destructive or financial), but could also be Execute depending on implementation.
From the tool's definition Tool name: lock_device_workspace — description is empty and uninformative
Documented attack patterns abuse exactly the kind of access lock_device_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_device_workspace:
{
"version": "1",
"default": "deny",
"tools": {
"lock_device_workspace": {
"limits": [
{
"counter": "lock_device_workspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}lock_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.
Free to start. No card required.
lock_device_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_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.
lock_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 lock_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 lock_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.
lock_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.
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.