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

storage_get_path_permissions

Get current permissions for a path.

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/storage-get-path-permissions.md

What storage_get_path_permissions does on Aapanel

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

This tool queries and retrieves existing file/directory permission information without altering data or triggering external operations. It is purely informational. Severity is low as permission metadata disclosure is a low-risk read operation in isolation, though the broader context of a server management tool means this could be part of a reconnaissance chain.

From the tool's definition Tool name 'storage_get_path_permissions' with description 'Get current permissions for a path' — uses verb 'get' indicating retrieval of existing data with no modification.

Questions about storage_get_path_permissions

What does the storage_get_path_permissions tool do? +

Get current permissions for a path. 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 storage_get_path_permissions? +

Register the Aapanel MCP server in PolicyLayer and add a rule for storage_get_path_permissions: 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 storage_get_path_permissions? +

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

Can I rate-limit storage_get_path_permissions? +

Yes. Add a rate_limit block to the storage_get_path_permissions 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 storage_get_path_permissions completely? +

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

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