check_package_python_compatibility
AI agents call check_package_python_compatibility to retrieve information from PyPI Query MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve or analyze package compatibility information from PyPI, a read-only operation with no capacity to modify, delete, or execute code. The tool does not move resources, trigger external actions, or modify data. The empty description reduces confidence slightly, but the consistent naming pattern across a query-focused server and lack of any destructive verbs make Read the clear category.
From the tool's definition Tool name 'check_package_python_compatibility' combined with server context indicates it queries compatibility data. Sibling tools like 'get_package_compatible_python_versions' and 'get_package_dependencies' are clearly Read operations.
Documented attack patterns abuse exactly the kind of access check_package_python_compatibility gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PyPI Query MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_package_python_compatibility:
{
"version": "1",
"default": "deny",
"tools": {
"check_package_python_compatibility": {}
}
}check_package_python_compatibility 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.
check_package_python_compatibility. It is categorised as a Read tool in the PyPI Query MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PyPI Query MCP Server MCP server in PolicyLayer and add a rule for check_package_python_compatibility: 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 PyPI Query MCP Server. Nothing to install.
check_package_python_compatibility 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 check_package_python_compatibility 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 check_package_python_compatibility. 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.
check_package_python_compatibility is provided by the PyPI Query MCP Server MCP server (loonghao/pypi-query-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PyPI Query MCP 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.
10 PyPI Query MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.