check_app_integrity
Verify integrity of a specific Nextcloud app by checking file signatures against its official release
This record as markdown: /tools/aiquila-nextcloud-mcp-server/check-app-integrity.md
What check_app_integrity does on AIquila — Nextcloud MCP Server
AI agents call check_app_integrity to retrieve information from AIquila — Nextcloud MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
appId | string | Yes | The app ID to check (e.g., "tasks", "deck", "photos") |
Parameters from the server's own tool schema.
Why check_app_integrity is rated Low
This tool performs cryptographic verification of app file signatures against known good releases. It retrieves and compares data (file signatures) but makes no changes to files, executes no arbitrary code, and has no side effects. It is purely a read/query operation for security auditing purposes. The severity is low because misuse would only result in false integrity reports, not system compromise or data loss.
From the tool's definition Tool name is 'check_app_integrity' and description states it 'Verify integrity of a specific Nextcloud app by checking file signatures against its official release' — this is a verification/inspection operation with no modification, deletion, or execution of…
Attacks that exploit this kind of access
The rule that runs check_app_integrity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_app_integrity, this is the rule to start with:
check_app_integrity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every check_app_integrity call is checked against it from then on.
Questions about check_app_integrity
Verify integrity of a specific Nextcloud app by checking file signatures against its official release. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.
check_app_integrity accepts 1 parameter: appId. Required: appId. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for check_app_integrity: 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 AIquila — Nextcloud MCP Server. Nothing to install.
check_app_integrity 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_app_integrity 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_app_integrity. 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_app_integrity is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
This server
Across the catalogue