This record as markdown: /tools/aapanel-mcp/project-get-config.md
What project_get_config does on Aapanel
AI agents call project_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 project_get_config is rated Low
This tool retrieves configuration information with no side effects. The verb 'get' and lack of any language suggesting modification, deletion, or execution clearly indicates a read-only operation. The blast radius is minimal—exposure of configuration data may inform an attacker but does not directly alter system state or execute operations.
From the tool's definition Tool name contains 'get' and description states 'Get project configuration' — retrieving configuration data without modification.
Attacks that exploit this kind of access
The rule that runs project_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 project_get_config, this is the rule to start with:
project_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 project_get_config call is checked against it from then on.
Questions about project_get_config
Get project 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 project_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.
project_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 project_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 project_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.
project_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