process_text
Submit a text-processing task to Nextcloud's AI framework and return the task ID. Use get_task_result to poll until it completes. Common task types: 'core:text2text' (free prompt), 'core:summarize' (summary), 'core:headline' (headline), 'core:extract_topics' (topics).
This record as markdown: /tools/aiquila-nextcloud-mcp-server/process-text.md
What process_text does on AIquila — Nextcloud MCP Server
AI agents invoke process_text 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 |
|---|---|---|---|
input | string | Yes | The text to process |
customId | string | — | Optional identifier to tag the task for later retrieval |
taskType | string | Yes | Task type ID (e.g. 'core:summarize', 'core:headline', 'core:extract_topics', 'core:text2text') |
Parameters from the server's own tool schema.
Why process_text is rated High
This tool triggers execution of an AI processing task on an external framework. It initiates a compute operation with side effects (task creation, resource consumption, AI inference) rather than simply reading data or writing a document.
From the tool's definition Submit a text-processing task to Nextcloud's AI framework and return the task ID
Attacks that exploit this kind of access
The rule that runs process_text 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 process_text, this is the rule to start with:
process_text 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 process_text call is checked against it from then on.
Questions about process_text
Submit a text-processing task to Nextcloud's AI framework and return the task ID. Use get_task_result to poll until it completes. Common task types: 'core:text2text' (free prompt), 'core:summarize' (summary), 'core:headline' (headline), 'core:extract_topics' (topics). 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.
process_text accepts 3 parameters: input, customId, taskType. Required: input, taskType. 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 process_text: 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.
process_text 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 process_text 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 process_text. 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.
process_text 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