Use this when starting work on a Jira ticket.
AI agents call get_task_context to retrieve information from DevsContext without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads and retrieves data from Jira tickets without modifying state. However, severity is medium rather than low because context about requirements and architectural decisions could potentially be used by an AI agent to make incorrect or risky decisions if the information is stale, incomplete, or misinterpreted—though the tool itself performs no destructive or side-effect actions.
From the tool's definition Tool is invoked 'when starting work on a Jira ticket' and fetches context from Jira. Description does not indicate modification, deletion, or execution—it retrieves synthesized engineering information (requirements, decisions, architecture, standards) on…
Attacks that exploit this kind of access
Use this when starting work on a Jira ticket. It is categorised as a Read tool in the DevsContext MCP Server, which means it retrieves data without modifying state.
Register the DevsContext 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 DevsContext. 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 DevsContext MCP server (pro0f/devscontext). 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 →