Get version information for Python tools (python, pip, uv, poetry, pyright, ruff, pytest) with caching
AI agents call python_version to retrieve information from MCP DevTools Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves version metadata about Python development tools. It has no side effects, does not execute arbitrary code, does not modify files or state, and does not interact with financial systems. The caching mechanism further confirms it is a simple read operation. This is a straightforward information lookup utility with minimal security risk.
From the tool's definition Tool description states it "Get[s] version information" for Python tools. The verb 'get' and the focus on version information retrieval with caching indicates a read-only operation that queries tool versions without modifying or executing code.
Documented attack patterns abuse exactly the kind of access python_version gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for python_version:
{
"version": "1",
"default": "deny",
"tools": {
"python_version": {}
}
}python_version 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 version information for Python tools (python, pip, uv, poetry, pyright, ruff, pytest) with caching. It is categorised as a Read tool in the MCP DevTools Server MCP Server, which means it retrieves data without modifying state.
Register the MCP DevTools Server MCP server in PolicyLayer and add a rule for python_version: 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 DevTools Server. Nothing to install.
python_version 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 python_version 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 python_version. 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.
python_version is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools 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.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.