Set the current project/context for task operations
AI agents use task_context_set to create or update resources in Mcp Taskwarrior Ai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Taskwarrior Ai environment.
An AI agent can call task_context_set faster than any human can review — one bad instruction and it creates or modifies resources in Mcp Taskwarrior Ai by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Set the current project/context for task operations. It is categorised as a Write tool in the Mcp Taskwarrior Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Taskwarrior Ai MCP server in PolicyLayer and add a rule for task_context_set: 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 Mcp Taskwarrior Ai. Nothing to install.
task_context_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the task_context_set 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 task_context_set. 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.
task_context_set is provided by the Mcp Taskwarrior Ai MCP server (storypixel/mcp-taskwarrior-ai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.