AI agents call search_aur 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 AUR package information without side effects. It does not install, modify, delete, or execute anything—it only fetches metadata from the AUR repository. This is a classic Read operation with minimal risk.
From the tool's definition Tool performs a search operation via AUR RPC API, returning metadata (votes, popularity, maintainer, outdated status).
Attacks that exploit this kind of access
Search the AUR via RPC. Returns votes/popularity/maintainer/outdated. 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_aur: 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_aur 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_aur 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_aur. 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_aur 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 →