get_task_context

Retrieve implementation notes and context saved for a task. Context contains developer notes, code snippets, decisions, or any text added via add_context_to_task. Use to understand previous work or decisions on a task.

Server Nubis @lil2good/nubis-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_task_context does on Nubis

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

Why get_task_context needs a policy

This tool purely queries and returns existing data (implementation notes, code snippets, decisions) without any side effects, modifications, or state changes. It is a straightforward read operation on task metadata, making it the lowest risk category with minimal security impact if misused by an AI agent.

From the tool's definition Tool description states it 'Retrieve[s] implementation notes and context saved for a task' with no mention of modification, deletion, or execution capabilities.

Questions about get_task_context

What does the get_task_context tool do? +

Retrieve implementation notes and context saved for a task. Context contains developer notes, code snippets, decisions, or any text added via add_context_to_task. Use to understand previous work or decisions on a task. It is categorised as a Read tool in the Nubis MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_task_context? +

Register the Nubis MCP server in PolicyLayer and add a rule for get_task_context: 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.

What risk level is get_task_context? +

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

Can I rate-limit get_task_context? +

Yes. Add a rate_limit block to the get_task_context 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_context completely? +

Set action: deny in the PolicyLayer policy for get_task_context. 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_context? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.