Critical-risk tools in Better Bear
5 of the 34 tools in Better Bear are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
bear_context_removeDestructive 4/5Remove a Bear note from the context library by removing its #context tag. Triggers a sync to delete the local file.
-
bear_context_remove_externalDestructive 5/5Remove a file from the external/ directory in the context library. Deletes the file and regenerates the index. Use when external content is no longer needed.
-
bear_delete_tagDestructive 4/5Delete a tag from all Bear notes. The tag text is removed but notes are preserved.
-
bear_remove_tagDestructive 4/5Remove a tag from a specific Bear note.
-
bear_trash_noteDestructive 4/5Move a Bear note to the trash. This is a soft delete — the note can be recovered from Bear's trash. The note is identified by its ID.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Better Bear
Enforce policy on Better Bear
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init