Get complete details for a single task including subtasks, comments, and blocker information. Use after get_tasks to dive deeper into a specific task. Returns full task object with nested subtasks and comments arrays.
AI agents call get_task_details to retrieve information from Nubis without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves task information (details, subtasks, comments, blockers) without creating, modifying, or deleting any data. It is a straightforward read operation with no side effects. The blast radius of misuse is minimal — an attacker could gain visibility into task details but cannot alter state or trigger external operations.
From the tool's definition Tool description states it 'Get[s] complete details for a single task' and 'Returns full task object' — purely retrieval operations with no modification, deletion, or execution.
Attacks that exploit this kind of access
Get complete details for a single task including subtasks, comments, and blocker information. Use after get_tasks to dive deeper into a specific task. Returns full task object with nested subtasks and comments arrays. It is categorised as a Read tool in the Nubis MCP Server, which means it retrieves data without modifying state.
Register the Nubis MCP server in PolicyLayer and add a rule for get_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 Nubis. Nothing to install.
get_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_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_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_task_details is provided by the Nubis MCP server (@lil2good/nubis-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →