get_group_root_files
Get group root directory file list
This record as markdown: /tools/1021143806-napcat-mcp/get-group-root-files.md
What get_group_root_files does on NapCat MCP Server
AI agents call get_group_root_files to retrieve information from NapCat 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_group_root_files is rated Low
This tool retrieves a list of files from a group's root directory. It performs no side effects, creates no data, executes no commands, and deletes nothing. It is a pure read operation. The severity is low because unauthorized file listing in a group context has minimal blast radius compared to destructive or financial operations, though it could leak sensitive information if access controls fail.
From the tool's definition Tool name is 'get_group_root_files' with description 'Get group root directory file list' — uses the verb 'Get' indicating retrieval without modification. The operation is a query/list action.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_group_root_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and NapCat MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_group_root_files, this is the rule to start with:
get_group_root_files 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 NapCat MCP Server, apply this rule, and every get_group_root_files call is checked against it from then on.
Questions about get_group_root_files
Get group root directory file list. It is categorised as a Read tool in the NapCat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for get_group_root_files: 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 NapCat MCP Server. Nothing to install.
get_group_root_files 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_group_root_files 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_group_root_files. 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_group_root_files is provided by the NapCat MCP Server MCP server (1021143806/napcat_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on NapCat MCP Server, and thousands of servers like it.
This server
Across the catalogue