[LIFECYCLE] Check for available system updates without applying them. Only works on Arch Linux systems. Requires pacman-contrib package. Safe read-only operation that shows pending updates. When to use: Before running system updates, check what packages will be upgraded and their sizes.
AI agents call check_updates_dry_run 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 and queries information about available system updates without creating, modifying, deleting, or executing any changes. It is purely informational—a read-only query of the package management system. The dry-run nature and explicit statement that it 'only checks' without applying updates confirms this is a Read category tool with minimal risk.
From the tool's definition Tool description explicitly states 'Safe read-only operation that shows pending updates' and 'without applying them'. The name includes 'dry_run' which further indicates no modifications occur.
Documented attack patterns abuse exactly the kind of access check_updates_dry_run 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 check_updates_dry_run:
{
"version": "1",
"default": "deny",
"tools": {
"check_updates_dry_run": {}
}
}check_updates_dry_run 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.
[LIFECYCLE] Check for available system updates without applying them. Only works on Arch Linux systems. Requires pacman-contrib package. Safe read-only operation that shows pending updates. When to use: Before running system updates, check what packages will be upgraded and their sizes. 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 check_updates_dry_run: 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.
check_updates_dry_run 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 check_updates_dry_run 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 check_updates_dry_run. 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.
check_updates_dry_run 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.