Remove package from pyproject.toml file and update the virtual environment. Returns True if successful.
AI agents call remove_package to permanently remove resources in Venv — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a package entry from pyproject.toml and modifies the virtual environment accordingly. While the pyproject.toml could be restored from version control, the action itself is a destructive modification — removing a dependency could break the project, and the operation is not transactional or easily undone.
From the tool's definition Remove package from pyproject.toml file and update the virtual environment
Documented attack patterns abuse exactly the kind of access remove_package gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Venv, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_package:
{
"version": "1",
"default": "deny",
"hide": [
"remove_package"
]
}remove_package disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove package from pyproject.toml file and update the virtual environment. Returns True if successful. It is categorised as a Destructive tool in the Venv MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Venv MCP server in PolicyLayer and add a rule for remove_package: 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 Venv. Nothing to install.
remove_package is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_package 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 remove_package. 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.
remove_package is provided by the Venv MCP server (sparfenyuk/venv-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Venv, 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.
6 Venv tools catalogued and risk-classified — across an index of 43,000+ MCP servers.