Remove a package from a project
AI agents call remove_package to permanently remove resources in Prowpt MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a package permanently deletes it from the project's dependency list. This action cannot be trivially undone without explicitly re-adding the package, making it destructive in nature. The blast radius is medium as it could break functionality dependent on that package.
From the tool's definition 'Remove a package from a project' — removing a package is an irreversible deletion of a dependency from the project configuration
Attacks that exploit this kind of access
Remove a package from a project. It is categorised as a Destructive tool in the Prowpt MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Prowpt MCP Server 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 Prowpt MCP Server. 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 Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
remove_package is one line of Prowpt MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →