Get detailed information about a specific administrator user.
AI agents call get_admin_user 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.
This tool retrieves information about administrator users without modifying, executing code, deleting, or performing financial operations. While the queried information (admin user details) may be sensitive from a business perspective, the tool itself performs a read-only operation with minimal blast radius if misused by an AI agent—it would only expose existing user information, not compromise systems or data…
From the tool's definition Tool name 'get_admin_user' and description 'Get detailed information about a specific administrator user' indicate a retrieval operation with no side effects. The verb 'Get' and lack of any modification language confirm this is a query action.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access get_admin_user 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_admin_user:
{
"version": "1",
"default": "deny",
"tools": {
"get_admin_user": {}
}
}get_admin_user 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 detailed information about a specific administrator user. 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_admin_user: 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_admin_user 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_admin_user 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_admin_user. 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_admin_user 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.