Detects and returns the current package manager information
AI agents call get_package_manager to retrieve information from Starwind UI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs detection and information retrieval about the package manager configuration. It does not create, modify, delete, execute commands, or trigger side effects—it simply queries and returns data about the current environment. This is a classic Read operation with minimal security risk.
From the tool's definition Tool name 'get_package_manager' and description 'Detects and returns the current package manager information' indicate a query/detection operation that retrieves existing system state without modification.
Documented attack patterns abuse exactly the kind of access get_package_manager gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Starwind UI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_package_manager:
{
"version": "1",
"default": "deny",
"tools": {
"get_package_manager": {}
}
} get_package_manager is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Detects and returns the current package manager information. It is categorised as a Read tool in the Starwind UI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Starwind UI MCP Server MCP server in PolicyLayer and add a rule for get_package_manager: 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 Starwind UI MCP Server. Nothing to install.
get_package_manager 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 get_package_manager 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 get_package_manager. 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.
get_package_manager is provided by the Starwind UI MCP Server MCP server (starwind-ui/starwind-ui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Starwind UI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Starwind UI MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.