This record as markdown: /tools/aapanel-mcp/site-get-config.md
What site_get_config does on Aapanel
AI agents call site_get_config 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 site_get_config is rated Low
This tool retrieves configuration data without modifying, deleting, or executing anything. While configuration details could be sensitive information useful for reconnaissance, the tool itself performs no destructive or side-effect operations.
From the tool's definition Tool name 'site_get_config' with description 'Get site configuration' — the verb 'get' and absence of any modification language indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs site_get_config 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 site_get_config, this is the rule to start with:
site_get_config 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 site_get_config call is checked against it from then on.
Questions about site_get_config
Get site configuration. 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 site_get_config: 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.
site_get_config 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 site_get_config 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 site_get_config. 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.
site_get_config 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