Mark a task as completed. This will automatically unblock dependent tasks.
AI agents use farnsworth_project_complete_task to create or update resources in Farnsworth — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Farnsworth environment.
This tool modifies task state from incomplete to completed and triggers cascading updates to dependent tasks. It is reversible (a completed task can typically be reopened in project management systems) and has no financial or destructive properties. The blast radius is medium because incorrect task completion could mislead project status tracking, but it does not irreversibly delete data or execute arbitrary code.
From the tool's definition Tool name contains 'complete' and description states 'Mark a task as completed' and 'will automatically unblock dependent tasks' — these are state modifications to task records.
Documented attack patterns abuse exactly the kind of access farnsworth_project_complete_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Farnsworth, and nothing reaches the server without passing your rules. This is the rule we recommend for farnsworth_project_complete_task:
{
"version": "1",
"default": "deny",
"tools": {
"farnsworth_project_complete_task": {
"limits": [
{
"counter": "farnsworth_project_complete_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}farnsworth_project_complete_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Mark a task as completed. This will automatically unblock dependent tasks. It is categorised as a Write tool in the Farnsworth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Farnsworth MCP server in PolicyLayer and add a rule for farnsworth_project_complete_task: 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 Farnsworth. Nothing to install.
farnsworth_project_complete_task 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 farnsworth_project_complete_task 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 farnsworth_project_complete_task. 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.
farnsworth_project_complete_task is provided by the Farnsworth MCP server (timowhite88/farnsworth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 Farnsworth tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
20 Farnsworth tools catalogued and risk-classified — across an index of 42,500+ MCP servers.