AI agents use farnsworth_project_update 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 creates or modifies data reversibly—it updates project information without permanently deleting it. The change can be undone by subsequent updates. This fits the Write category. Severity is medium because unauthorized project updates could disrupt workflows or corrupt project state, but the impact is typically confined to the local Farnsworth instance and reversible.
From the tool's definition Tool name 'farnsworth_project_update' and description 'Update an existing project' indicate the tool modifies existing data (project records) in a reversible manner.
Documented attack patterns abuse exactly the kind of access farnsworth_project_update 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_update:
{
"version": "1",
"default": "deny",
"tools": {
"farnsworth_project_update": {
"limits": [
{
"counter": "farnsworth_project_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}farnsworth_project_update 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.
Update an existing project. 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_update: 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_update 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_update 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_update. 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_update 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.