update
Updates dependencies in the lock file. Optionally updates a single package.
This record as markdown: /tools/io-github-dave-london-lint/update.md
What update does on Lint
AI agents use update to create or update resources in Lint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lint environment.
Why update is rated Medium
This tool modifies the lock file (package dependencies) in a reversible manner. It is a Write operation because it creates or modifies data (dependency versions/references) rather than executing arbitrary code, deleting files, or moving money.
From the tool's definition Tool name 'update' with description 'Updates dependencies in the lock file. Optionally updates a single package.' indicates modification of dependency metadata without deletion or code execution.
Attacks that exploit this kind of access
The rule that runs update safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Lint, apply this rule, and every update call is checked against it from then on.
Questions about update
Updates dependencies in the lock file. Optionally updates a single package. It is categorised as a Write tool in the Lint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lint MCP server in PolicyLayer and add a rule for 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 Lint. Nothing to install.
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 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 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.
update is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lint, and thousands of servers like it.
This server
Across the catalogue