auth user(계정) 목록 조회.
AI agents call list_auth_users_tool to retrieve information from F5 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that lists existing auth users. It retrieves data without creating, modifying, deleting, or executing any changes to F5 configuration. The low severity reflects minimal blast radius—listing users is informational only and cannot cause system damage or data loss if misused by an AI agent.
From the tool's definition Tool name contains 'list' and description states '목록 조회' (list inquiry/retrieval). The tool retrieves or queries authentication user account information with no indication of modification, deletion, or side effects.
Attacks that exploit this kind of access
auth user(계정) 목록 조회. It is categorised as a Read tool in the F5 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the F5 MCP Server MCP server in PolicyLayer and add a rule for list_auth_users_tool: 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 F5 MCP Server. Nothing to install.
list_auth_users_tool 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 list_auth_users_tool 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 list_auth_users_tool. 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.
list_auth_users_tool is provided by the F5 MCP Server MCP server (mink0119/f5-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →