Get pure task context without file paths - for current or specified task
AI agents call get_task_context to retrieve information from Agent Communication 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 contextual information about tasks without side effects. It queries existing data (task context) without creating, modifying, deleting, or executing anything. The explicit mention of excluding 'file paths' further confirms it is a read-only retrieval operation. Severity is low because misuse would only expose task metadata with no ability to alter systems or data.
From the tool's definition Tool name 'get_task_context' and description 'Get pure task context without file paths - for current or specified task' indicate retrieval of task metadata and context information.
Attacks that exploit this kind of access
Get pure task context without file paths - for current or specified task. It is categorised as a Read tool in the Agent Communication MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Agent Communication MCP Server 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 Agent Communication MCP Server. Nothing to install.
get_task_context 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_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.
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.
get_task_context is provided by the Agent Communication MCP Server MCP server (jerfowler/agent-comm-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 →