tamper_set_dir_protection
Enable or disable directory protection for a site (toggle .user.ini cross-site protection).
This record as markdown: /tools/aapanel-mcp/tamper-set-dir-protection.md
What tamper_set_dir_protection does on Aapanel
AI agents use tamper_set_dir_protection to create or update resources in Aapanel, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aapanel environment.
Why tamper_set_dir_protection is rated Medium
The tool modifies PHP security configuration (.user.ini) to enable or disable cross-site protection—a reversible change to site settings. This is Write-category behavior (creates/modifies data reversibly). Severity is high because disabling directory protection exposes web applications to directory traversal and cross-site execution attacks, with significant blast radius on site security posture.
From the tool's definition Tool enables or disables directory protection via .user.ini configuration modification ('toggle .user.ini cross-site protection'). This modifies server configuration state reversibly.
Attacks that exploit this kind of access
The rule that runs tamper_set_dir_protection 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 tamper_set_dir_protection, this is the rule to start with:
tamper_set_dir_protection 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 Aapanel, apply this rule, and every tamper_set_dir_protection call is checked against it from then on.
Questions about tamper_set_dir_protection
Enable or disable directory protection for a site (toggle .user.ini cross-site protection). It is categorised as a Write tool in the Aapanel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aapanel MCP server in PolicyLayer and add a rule for tamper_set_dir_protection: 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.
tamper_set_dir_protection 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 tamper_set_dir_protection 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 tamper_set_dir_protection. 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.
tamper_set_dir_protection 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