restore
Runs dotnet restore to restore NuGet dependencies and returns structured results.
This record as markdown: /tools/io-github-dave-london-lint/restore.md
What restore does on Lint
AI agents use restore 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 restore is rated Medium
The tool performs a dependency restoration operation that modifies the project environment by downloading and writing NuGet packages and updating dependency metadata. While this is reversible (dependencies can be cleared and re-restored), it materially alters the project state and involves external network operations. This fits the Write category (creates/modifies data reversibly) rather than Read.
From the tool's definition Tool 'restore' runs 'dotnet restore to restore NuGet dependencies'. This modifies the local project state by downloading and installing package dependencies, which are reversible changes to the project's dependency tree and lock files.
Attacks that exploit this kind of access
The rule that runs restore 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 restore, this is the rule to start with:
restore 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 restore call is checked against it from then on.
Questions about restore
Runs dotnet restore to restore NuGet dependencies and returns structured results. 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 restore: 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.
restore 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 restore 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 restore. 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.
restore 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