update_php_config
Update PHP configuration directives for a hosting package
This record as markdown: /tools/cbrown35-20i-mcp/update-php-config.md
What update_php_config does on 20i MCP Server
AI agents use update_php_config to create or update resources in 20i MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 20i MCP Server environment.
Why update_php_config is rated Medium
This tool modifies PHP configuration directives, which are settings that control how PHP behaves on a hosting package. Such changes are reversible (configurations can be reverted or reconfigured), placing this in the Write category rather than Execute or Destructive.
From the tool's definition Tool name is 'update_php_config' and description states 'Update PHP configuration directives for a hosting package' — the verb 'Update' indicates modification of configuration data.
Attacks that exploit this kind of access
The rule that runs update_php_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_php_config, this is the rule to start with:
update_php_config stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every update_php_config call is checked against it from then on.
Questions about update_php_config
Update PHP configuration directives for a hosting package. It is categorised as a Write tool in the 20i MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for update_php_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 20i MCP Server. Nothing to install.
update_php_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_php_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 update_php_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.
update_php_config is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue