Search the Winget package repository for application metadata including installer URLs, versions, and silent install arguments
AI agents call search_winget to retrieve information from Packager-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a public package repository (Winget) and returns metadata such as installer URLs, versions, and installation arguments. It performs only read/search operations without creating, modifying, deleting, or executing code. The worst-case misuse scenario is retrieval of metadata for an unintended application, which poses minimal risk compared to tools that execute, write, or delete data.
From the tool's definition Tool name 'search_winget' and description state it 'Search[es] the Winget package repository for application metadata including installer URLs, versions, and silent install arguments' — purely retrieval of metadata with no side effects.
Attacks that exploit this kind of access
Search the Winget package repository for application metadata including installer URLs, versions, and silent install arguments. It is categorised as a Read tool in the Packager-MCP MCP Server, which means it retrieves data without modifying state.
Register the Packager- MCP server in PolicyLayer and add a rule for search_winget: 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 Packager-MCP. Nothing to install.
search_winget 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 search_winget 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 search_winget. 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.
search_winget is provided by the Packager- MCP server (kkaminsk/packager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →