Delete code artifact (cascades memory associations). WHEN: Removing obsolete, incorrect, or no-longer-relevant code artifacts. BEHAVIOR: Permanently deletes artifact and removes memory associations. Memories themselves are preserved. Cannot be undone. NOT-USE: For temporary hiding (no undo availa...
AI agents call delete_code_artifact to permanently remove resources in Forgetful — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently and irreversibly deletes code artifacts from the knowledge base with no recovery mechanism. While the blast radius is somewhat contained to individual artifacts (not the entire database), the permanent nature and explicit 'cannot be undone' language make this a Destructive operation.
From the tool's definition Tool description states: 'Permanently deletes artifact and removes memory associations. Cannot be undone.' The name includes 'delete' and the description explicitly warns 'Cannot be undone' and advises against use 'For temporary hiding (no undo available)'.
Documented attack patterns abuse exactly the kind of access delete_code_artifact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_code_artifact:
{
"version": "1",
"default": "deny",
"hide": [
"delete_code_artifact"
]
}delete_code_artifact 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.
Delete code artifact (cascades memory associations). WHEN: Removing obsolete, incorrect, or no-longer-relevant code artifacts. BEHAVIOR: Permanently deletes artifact and removes memory associations. Memories themselves are preserved. Cannot be undone. NOT-USE: For temporary hiding (no undo available), or updating (use update_code_artifact). Args: artifact_id: Artifact ID to delete ctx: Context (automatically injected) Returns: Success confirmation with deleted artifact ID Raises: ToolError if artifact not found. It is categorised as a Destructive tool in the Forgetful MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Forgetful MCP server in PolicyLayer and add a rule for delete_code_artifact: 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 Forgetful. Nothing to install.
delete_code_artifact 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_code_artifact 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_code_artifact. 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_code_artifact is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Forgetful tools catalogued and risk-classified — across an index of 42,500+ MCP servers.