New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_task_result

Get the status and result of a Nextcloud AI task previously created by process_text or generate_image. Status: 1=scheduled, 2=running, 3=successful, 4=failed.

Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/get-task-result.md

What get_task_result does on AIquila — Nextcloud MCP Server

AI agents call get_task_result 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.

ParameterTypeRequiredDescription
taskId number Yes The task ID returned by process_text or generate_image

Parameters from the server's own tool schema.

Why get_task_result is rated Low

This is a pure retrieval operation that queries the state of an existing asynchronous task. It does not create, modify, delete, or execute anything—it only fetches and returns data about a task that was already initiated. The minimal blast radius (read-only access to task metadata) and lack of state changes classify it as Read with low severity.

From the tool's definition Tool retrieves status and result of a previously created task ('Get the status and result'), with no mutation or side effects. Returns only informational status codes and task output.

Questions about get_task_result

What does the get_task_result tool do? +

Get the status and result of a Nextcloud AI task previously created by process_text or generate_image. Status: 1=scheduled, 2=running, 3=successful, 4=failed. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_task_result accept? +

get_task_result accepts 1 parameter: taskId. Required: taskId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_task_result? +

Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for get_task_result: 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.

What risk level is get_task_result? +

get_task_result is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_task_result? +

Yes. Add a rate_limit block to the get_task_result 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.

How do I block get_task_result completely? +

Set action: deny in the PolicyLayer policy for get_task_result. 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.

What MCP server provides get_task_result? +

get_task_result 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AIquila — Nextcloud MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.