aiquila_test
Test AIquila Claude API integration with a simple prompt
This record as markdown: /tools/aiquila-nextcloud-mcp-server/aiquila-test.md
What aiquila_test does on AIquila — Nextcloud MCP Server
AI agents invoke aiquila_test to trigger actions in AIquila — Nextcloud MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
prompt | string | — | Test prompt to send to Claude API |
Parameters from the server's own tool schema.
Why aiquila_test is rated High
This tool triggers an external API call to the AIquila/Claude API by sending a prompt, which constitutes executing an external operation. While described as a 'test', it initiates a real API interaction with an external service. The severity is medium as misuse could result in unintended API calls or prompt injection, but the blast radius is limited compared to file or data manipulation tools.
From the tool's definition Test AIquila Claude API integration with a simple prompt
Attacks that exploit this kind of access
The rule that runs aiquila_test 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 aiquila_test, this is the rule to start with:
aiquila_test stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 aiquila_test call is checked against it from then on.
Questions about aiquila_test
Test AIquila Claude API integration with a simple prompt. It is categorised as a Execute tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
aiquila_test accepts 1 parameter: prompt. 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 aiquila_test: 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.
aiquila_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the aiquila_test 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 aiquila_test. 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.
aiquila_test 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.
Across the catalogue