list_desktop_files
AI agents call list_desktop_files to retrieve information from Allcanuse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests it retrieves or enumerates files from a desktop directory without altering them. Despite the empty description lowering confidence slightly, the 'list_' prefix combined with the absence of any mutation-indicating keywords (create, delete, modify, execute) places this firmly in the Read category.
From the tool's definition Tool name 'list_desktop_files' indicates directory listing or file enumeration with no modification capability. The 'list_' prefix is a strong semantic indicator of read-only retrieval.
Documented attack patterns abuse exactly the kind of access list_desktop_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Allcanuse, and nothing reaches the server without passing your rules. This is the rule we recommend for list_desktop_files:
{
"version": "1",
"default": "deny",
"tools": {
"list_desktop_files": {}
}
}list_desktop_files is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_desktop_files. It is categorised as a Read tool in the Allcanuse MCP Server, which means it retrieves data without modifying state.
Register the Allcanuse MCP server in PolicyLayer and add a rule for list_desktop_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 Allcanuse. Nothing to install.
list_desktop_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 list_desktop_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 list_desktop_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.
list_desktop_files is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Allcanuse, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
130 Allcanuse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.