list_directories_by_name
AI agents call list_directories_by_name to retrieve information from Linux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing directories is a read operation that queries filesystem metadata without modification, deletion, or execution. No side effects occur beyond retrieving information. The read-only nature of the entire server, combined with the non-mutating sibling tools, confirms this tool retrieves data without causing changes.
From the tool's definition Tool name 'list_directories_by_name' indicates directory listing operation. Server description explicitly states 'read-only Linux system diagnostics.' All sibling tools are non-destructive information retrieval functions (get_audit_logs, get_cpu_info,…
Attacks that exploit this kind of access
list_directories_by_name. It is categorised as a Read tool in the Linux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linux MCP Server MCP server in PolicyLayer and add a rule for list_directories_by_name: 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 Linux MCP Server. Nothing to install.
list_directories_by_name 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_directories_by_name 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_directories_by_name. 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_directories_by_name is provided by the Linux MCP Server MCP server (narmaku/linux-mcp-server-archived). 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 →