This record as markdown: /tools/eaveluo-1panel-mcp/get-php-conf-file.md
What get_php_conf_file does on 1Panel MCP Server
AI agents call get_php_conf_file to retrieve information from 1Panel MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_php_conf_file is rated Low
This tool retrieves PHP configuration file content for inspection purposes. No side effects occur from querying configuration; it does not modify, delete, or execute any operations. Reading config files is fundamental operational visibility with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'get_php_conf_file' and description 'Get PHP config file' indicate a retrieval operation with no modification capability. The verb 'get' and absence of any write/delete/execute qualifiers confirm read-only semantics.
Attacks that exploit this kind of access
The rule that runs get_php_conf_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1Panel MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_php_conf_file, this is the rule to start with:
get_php_conf_file 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 1Panel MCP Server, apply this rule, and every get_php_conf_file call is checked against it from then on.
Questions about get_php_conf_file
Get PHP config file. It is categorised as a Read tool in the 1Panel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for get_php_conf_file: 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 1Panel MCP Server. Nothing to install.
get_php_conf_file 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_php_conf_file 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_php_conf_file. 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_php_conf_file is provided by the 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
This server
Across the catalogue