[ORGANIZATION] Unified tool for querying file-package ownership relationships. Supports three modes:
AI agents call query_file_ownership 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 or queries existing system information about file ownership and package relationships. There is no indication of side effects, data modification, deletion, code execution, or financial operations. It is a read-only diagnostic tool consistent with others on the server like 'get_official_package_info' and 'get_system_info'.
From the tool's definition Tool name is 'query_file_ownership' and description indicates it 'queries file-package ownership relationships.' The verb 'query' and 'supports three modes' (implying read-only inspection) indicate data retrieval with no modification.
Documented attack patterns abuse exactly the kind of access query_file_ownership 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_file_ownership:
{
"version": "1",
"default": "deny",
"tools": {
"query_file_ownership": {}
}
}query_file_ownership 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.
[ORGANIZATION] Unified tool for querying file-package ownership relationships. Supports three modes:. 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_file_ownership: 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_file_ownership 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_file_ownership 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_file_ownership. 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_file_ownership 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.