Get the current status and full details of a specific cloud task. Returns comprehensive information including status (CREATING, RUNNING, FINISHED, FAILED, CANCELLED), summary of work done, repository, branch, PR URL if created, and all configuration options. Usage Example: \
AI agents call get_task to retrieve information from Cloud Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the status and details of an existing task. It performs a read-only operation that returns information about task state, summary, repository, branch, PR URL, and configuration without creating, modifying, deleting, or executing any operations. No side effects or state changes occur.
From the tool's definition Tool name is 'get_task' and description states it 'Get the current status and full details of a specific cloud task' and 'Returns comprehensive information'. The verb 'Get' and 'Returns' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Cloud Agent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_task:
{
"version": "1",
"default": "deny",
"tools": {
"get_task": {}
}
} get_task 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.
Get the current status and full details of a specific cloud task. Returns comprehensive information including status (CREATING, RUNNING, FINISHED, FAILED, CANCELLED), summary of work done, repository, branch, PR URL if created, and all configuration options. Usage Example: \. It is categorised as a Read tool in the Cloud Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cloud Agent MCP Server MCP server in PolicyLayer and add a rule for get_task: 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 Cloud Agent MCP Server. Nothing to install.
get_task 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 get_task 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 get_task. 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.
get_task is provided by the Cloud Agent MCP Server MCP server (jxnl/cursor-cloud-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Cloud Agent MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Cloud Agent MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.