AI agents call list_local_directory to retrieve information from LuzzyTool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns directory contents without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security risk—the main concern would be information disclosure if sensitive file structures are exposed, but that is a low-severity read-category issue.
From the tool's definition Tool name 'list_local_directory' and description '列出指定本地目录下的所有文件和子目录' (list all files and subdirectories in a specified local directory) indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
【必须调用】列出指定本地目录下的所有文件和子目录。. It is categorised as a Read tool in the LuzzyTool MCP Server, which means it retrieves data without modifying state.
Register the LuzzyTool MCP server in PolicyLayer and add a rule for list_local_directory: 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 LuzzyTool. Nothing to install.
list_local_directory 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 list_local_directory 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 list_local_directory. 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.
list_local_directory is provided by the LuzzyTool MCP server (luzzymeow/luzzytool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →