AI agents call get_adom_lock_status to retrieve information from Fortimanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves lock status information from FortiManager's ADOM (Administrative Domain) object. This is a read-only operation that queries existing state without creating, modifying, deleting, or executing any operations. No side effects are expected. The description is empty, which slightly reduces confidence, but the naming convention clearly indicates a retrieval operation.
From the tool's definition Tool name 'get_adom_lock_status' uses the verb 'get', which indicates data retrieval. The prefix 'get_' and suffix 'status' suggest querying state information without modification.
Documented attack patterns abuse exactly the kind of access get_adom_lock_status 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 get_adom_lock_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_adom_lock_status": {}
}
}get_adom_lock_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_adom_lock_status. It is categorised as a Read tool in the Fortimanager MCP Server, which means it retrieves data without modifying state.
Register the Fortimanager MCP server in PolicyLayer and add a rule for get_adom_lock_status: 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.
get_adom_lock_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_adom_lock_status 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 get_adom_lock_status. 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.
get_adom_lock_status 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.