Get detailed information about a specific package
AI agents call package_info to retrieve information from Pacman without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves package metadata and information. There is no indication it modifies, deletes, executes, or creates any resources. It is purely informational/query functionality with no side effects.
From the tool's definition Tool name 'package_info' and description 'Get detailed information about a specific package' indicate data retrieval without modification.
Documented attack patterns abuse exactly the kind of access package_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pacman, and nothing reaches the server without passing your rules. This is the rule we recommend for package_info:
{
"version": "1",
"default": "deny",
"tools": {
"package_info": {}
}
}package_info 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.
Get detailed information about a specific package. It is categorised as a Read tool in the Pacman MCP Server, which means it retrieves data without modifying state.
Register the Pacman MCP server in PolicyLayer and add a rule for package_info: 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 Pacman. Nothing to install.
package_info 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 package_info 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 package_info. 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.
package_info is provided by the Pacman MCP server (oborchers/mcp-server-pacman). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pacman, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Pacman tools catalogued and risk-classified — across an index of 43,000+ MCP servers.