Critical Risk →

bear_context_remove_external

Remove 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.

Accepts file system path (filename)

Part of the Better Bear MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

better-bear Destructive Risk 5/5

AI agents may call bear_context_remove_external to permanently remove or destroy resources in Better Bear. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call bear_context_remove_external in a loop, permanently destroying resources in Better Bear. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-kuvopllc-better-bear.yaml
tools:
  bear_context_remove_external:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Better Bear policy for all 34 tools.

Tool Name bear_context_remove_external
Category Destructive
Risk Level Critical

View all 34 tools →

Agents calling destructive-class tools like bear_context_remove_external have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

bear_context_remove_external is one of the critical-risk operations in Better Bear. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the bear_context_remove_external tool do? +

Remove 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.. It is categorised as a Destructive tool in the Better Bear MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on bear_context_remove_external? +

Add a rule in your Intercept YAML policy under the tools section for bear_context_remove_external. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Better Bear MCP server.

What risk level is bear_context_remove_external? +

bear_context_remove_external is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bear_context_remove_external? +

Yes. Add a rate_limit block to the bear_context_remove_external rule in your Intercept 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.

How do I block bear_context_remove_external completely? +

Set action: deny in the Intercept policy for bear_context_remove_external. 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.

What MCP server provides bear_context_remove_external? +

bear_context_remove_external is provided by the Better Bear MCP server (better-bear). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Better Bear

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.