Permanently deletes a module and all its contents.
AI agents call delete_pynet_module to permanently remove resources in PyNet Bridge — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (a module and all associated contents) with no undo mechanism. Permanent deletion is the defining characteristic of the Destructive category. The high severity reflects the risk that an AI agent could accidentally delete important modules, configurations, or code.
From the tool's definition Tool description states 'Permanently deletes a module and all its contents.' The word 'permanently' indicates irreversible data loss.
Attacks that exploit this kind of access
Permanently deletes a module and all its contents. It is categorised as a Destructive tool in the PyNet Bridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PyNet Bridge MCP server in PolicyLayer and add a rule for delete_pynet_module: 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 PyNet Bridge. Nothing to install.
delete_pynet_module 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 delete_pynet_module 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 delete_pynet_module. 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.
delete_pynet_module is provided by the PyNet Bridge MCP server (rafael-nunezdearenas/pynetbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →