Get detailed information about a specific package
AI agents call get_package_details to retrieve information from MCP Code Analysis Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about a software package. It has no side effects, does not modify data, execute code, delete resources, or affect financial systems. It falls squarely into the Read category as a data retrieval operation. The low severity reflects minimal risk even if misused by an agent, as it only exposes existing package metadata without enabling destructive or executing actions.
From the tool's definition Tool name 'get_package_details' and description 'Get detailed information about a specific package' indicate a retrieval operation with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_package_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Code Analysis Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_package_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_package_details": {}
}
}get_package_details 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 MCP Code Analysis Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Code Analysis Server MCP server in PolicyLayer and add a rule for get_package_details: 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 MCP Code Analysis Server. Nothing to install.
get_package_details 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_details 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_details. 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_details is provided by the MCP Code Analysis Server MCP server (johannhartmann/mcpcodeanalysis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Code Analysis Server, 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.
44 MCP Code Analysis Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.