AI agents call search_system_repos 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 package information from Arch/CachyOS official repositories without modifying any system state. It is analogous to running 'pacman -Ss' to search repositories. No packages are installed, modified, or deleted. The blast radius of misuse is minimal—an agent could only enumerate available packages.
From the tool's definition Tool description states it 'Search[es] official pacman repos' and 'Returns name/repo/version/installed'. The verb 'search' and the nature of returned data (metadata about packages) indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
Search official pacman repos. Returns name/repo/version/installed. 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 search_system_repos: 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.
search_system_repos 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 search_system_repos 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 search_system_repos. 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.
search_system_repos 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 →