New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

tamper_get_dir_protection

Get directory protection status for a site (checks .user.ini and access controls).

SERVERAapanel SOURCEnipunanirmal/aapanel-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aapanel-mcp/tamper-get-dir-protection.md

What tamper_get_dir_protection does on Aapanel

AI agents call tamper_get_dir_protection 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 tamper_get_dir_protection is rated Low

This tool queries the current state of directory protection without altering, creating, or removing any data. It is purely informational and presents minimal risk if misused by an AI agent, as the worst outcome is information disclosure about existing protections.

From the tool's definition Tool name includes 'get' and description states 'Get directory protection status' — a retrieval operation that checks existing security settings (.user.ini and access controls) with no modification or deletion.

Questions about tamper_get_dir_protection

What does the tamper_get_dir_protection tool do? +

Get directory protection status for a site (checks .user.ini and access controls). It is categorised as a Read tool in the Aapanel MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tamper_get_dir_protection? +

Register the Aapanel MCP server in PolicyLayer and add a rule for tamper_get_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.

What risk level is tamper_get_dir_protection? +

tamper_get_dir_protection is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tamper_get_dir_protection? +

Yes. Add a rate_limit block to the tamper_get_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.

How do I block tamper_get_dir_protection completely? +

Set action: deny in the PolicyLayer policy for tamper_get_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.

What MCP server provides tamper_get_dir_protection? +

tamper_get_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Aapanel's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.