get_task_context

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-task-context.md

WHAT IT DOES

What get_task_context does on Trace

AI agents call get_task_context to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_task_context is rated Low

This tool retrieves and queries contextual information about code structure, dependencies, and execution paths from an already-built dependency graph. It has no side effects, does not execute code, and does not modify any data. It is a pure information retrieval operation, making it a Read category tool with low risk.

From the tool's definition Tool description states 'Read-only' and explicitly lists it as a retrieval operation that 'replaces manual chaining of search → get_symbol → Read'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_task_context safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_task_context, this is the rule to start with:

get_task_context Allowed

get_task_context is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_task_context": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_task_context call is checked against it from then on.

FAQ

Questions about get_task_context

What does the get_task_context tool do? +

All-in-one context for starting a dev task: execution paths, tests, entry points, adapted by task type. Use as your FIRST call when beginning any new task — replaces manual chaining of search → get_symbol → Read. For narrower feature-code lookup use get_feature_context instead. Read-only. Returns JSON (default) or Markdown. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_task_context? +

Register the Trace 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 Trace. 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 Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Trace, and thousands of servers like it.

This server

All 191 Trace tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →editor_context on 010 Editor →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →