FlowLink: MCP proxy blocking destructive AI agent commands
FlowLink is a new MCP proxy designed to prevent AI agents from executing harmful commands on production servers. It intercepts over 100 destructive commands before they can be executed and allows for customizable rules for each agent and tool. The setup is quick and requires no code changes, making it accessible for various AI agents.
- ▪FlowLink acts as a proxy between AI agents and production tools to prevent destructive commands.
- ▪It intercepts commands like 'rm -rf' and 'DROP TABLE' before execution.
- ▪The system includes a Telegram approval queue for high-risk operations.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48283348 |
| Publication time | Tue, 26 May 2026 18:01:25 +0000 |
| Retrieval time | 2026-05-26T18:07:50.919Z |
| Last seen | 2026-05-26T18:07:50.919Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | f5-ZNZ9POvbJ |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
We built FlowLink because AI agents (Claude Code, Cursor, Copilot) keep executing destructive commands on production servers with no guardrails.The recent "AI agent deleted production database" post (860 pts here) is exactly what this prevents.FlowLink is an MCP proxy between your AI agent and your tools. No code changes required. Point your agent config to FlowLink and it starts intercepting destructive commands.What it does:Shield Engine intercepts rm -rf, DROP TABLE, git push --force, chmod 777 and 100+ destructive patterns BEFORE execution.Policy Engine: per-agent, per-tool rules (e.g.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.