[HISTORY] Unified tool for querying package history from pacman logs. Supports four query types:
AI agents call query_package_history to retrieve information from Arch Linux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information from system logs (pacman package manager logs). It performs data retrieval operations only—no modifications, deletions, code execution, or external side effects. The 'four query types' mentioned are likely different filtering/search modes over the same log data. This is a typical Read category operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name and description indicate 'querying package history from pacman logs' with 'HISTORY' tag. The verb 'query' and the phrase 'querying package history' indicate retrieval of historical data without modification or execution of external operations.
Documented attack patterns abuse exactly the kind of access query_package_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Arch Linux, and nothing reaches the server without passing your rules. This is the rule we recommend for query_package_history:
{
"version": "1",
"default": "deny",
"tools": {
"query_package_history": {}
}
}query_package_history 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.
[HISTORY] Unified tool for querying package history from pacman logs. Supports four query types:. It is categorised as a Read tool in the Arch Linux MCP Server, which means it retrieves data without modifying state.
Register the Arch Linux MCP server in PolicyLayer and add a rule for query_package_history: 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 Arch Linux. Nothing to install.
query_package_history 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 query_package_history 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 query_package_history. 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.
query_package_history is provided by the Arch Linux MCP server (nihalxkumar/arch-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 Arch Linux tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
22 Arch Linux tools catalogued and risk-classified — across an index of 42,500+ MCP servers.