Retrieves details of the current task (first uncompleted task) with full context. This is the recommended tool to use when working with tasks.
AI agents call get_current_task_details to retrieve information from Divide and Conquer 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 information about task state and context without causing side effects. It is a straightforward data retrieval operation comparable to a 'get' or 'fetch' pattern, placing it firmly in the Read category. The low severity reflects that misuse would only expose task information already accessible to the agent within its working context, with no destructive or operational impact.
From the tool's definition Tool name 'get_current_task_details' and description 'Retrieves details of the current task' indicates a read-only operation that queries task data without modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get_current_task_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Divide and Conquer MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_task_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_task_details": {}
}
}get_current_task_details 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.
Retrieves details of the current task (first uncompleted task) with full context. This is the recommended tool to use when working with tasks. It is categorised as a Read tool in the Divide and Conquer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Divide and Conquer MCP Server MCP server in PolicyLayer and add a rule for get_current_task_details: 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 Divide and Conquer MCP Server. Nothing to install.
get_current_task_details 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_current_task_details 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_current_task_details. 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_current_task_details is provided by the Divide and Conquer MCP Server MCP server (landicefu/divide-and-conquer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Divide and Conquer 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.
15 Divide and Conquer MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.