list-package
Runs dotnet list package and returns structured NuGet package listings per project and framework.
This record as markdown: /tools/io-github-dave-london-git/list-package.md
What list-package does on Git
AI agents call list-package to retrieve information from Git without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list-package is rated Low
This tool queries and retrieves NuGet package information from a .NET project. It is a read-only operation that lists dependencies and their versions, similar to 'list' or 'get' operations. It has no side effects, does not modify files, execute commands, delete data, or move funds. The blast radius of misuse is minimal - an agent could only retrieve package information that is already present in the project manifest.
From the tool's definition Tool name 'list-package' and description indicates it 'Runs dotnet list package and returns structured NuGet package listings' - a query operation that retrieves package metadata without modifying state.
Attacks that exploit this kind of access
The rule that runs list-package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list-package, this is the rule to start with:
list-package is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every list-package call is checked against it from then on.
Questions about list-package
Runs dotnet list package and returns structured NuGet package listings per project and framework. It is categorised as a Read tool in the Git MCP Server, which means it retrieves data without modifying state.
Register the Git MCP server in PolicyLayer and add a rule for list-package: 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 Git. Nothing to install.
list-package is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list-package 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 list-package. 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.
list-package is provided by the Git 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 Git, and thousands of servers like it.
This server
Across the catalogue