This record as markdown: /tools/aapanel-mcp/config-get-users.md
What config_get_users does on Aapanel
AI agents call config_get_users to retrieve information from Aapanel without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why config_get_users is rated Low
This tool retrieves and displays existing panel user data. No data is created, modified, deleted, or executed. The blast radius is low—exposure allows an attacker to enumerate users but does not grant direct access to perform actions as those users or modify their configurations. This is consistent with the Read category for query/list operations with no side effects.
From the tool's definition Tool name 'config_get_users' and description 'List panel users' indicate retrieval of user information without modification. The verb 'List' is a classic read operation.
Attacks that exploit this kind of access
The rule that runs config_get_users safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For config_get_users, this is the rule to start with:
config_get_users is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every config_get_users call is checked against it from then on.
Questions about config_get_users
List panel users. It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.
Register the Aapanel MCP server in PolicyLayer and add a rule for config_get_users: 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 Aapanel. Nothing to install.
config_get_users 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 config_get_users 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 config_get_users. 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.
config_get_users is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
This server
Across the catalogue