AI agents call list_package_files to retrieve information from Cachyos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about files installed by packages using pacman's list functionality. It has no side effects, does not modify, delete, or execute anything — it purely reads and filters data from the package database. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool description states 'Files installed by a package (``pacman -Ql``)' — pacman -Ql is a query operation that lists files without modification. The name 'list_package_files' and description 'bounded/filterable' indicate data retrieval only.
Attacks that exploit this kind of access
Files installed by a package (pacman -Ql), bounded/filterable. It is categorised as a Read tool in the Cachyos MCP Server, which means it retrieves data without modifying state.
Register the Cachyos MCP server in PolicyLayer and add a rule for list_package_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 Cachyos. Nothing to install.
list_package_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_package_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_package_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_package_files is provided by the Cachyos MCP server (raindancer118/cachyos-mcp). 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 →