I gave my AI agent one harmless permission. It became a backdoor for everyone
Ai Agents In ActionCybersecurityLLMOpen SourceI gave my AI agent one harmless permission. It became a backdoor for everyone.Roeehersh5 min read·1 hour ago--ListenShareHow one write path in a helpful bot turned into a permission problem, and the small service I built to close it.Press enter or click to view image in full sizeThe agentI built an ops agent at work. You ask it what’s wrong with a service and it comes back in about fifteen seconds with:error rate and latencypod restarts and Kubernetes eventsnode statusthe last pipeline that touched the service, and why it failed if it didA person clicking through dashboards takes ten minutes to get the same picture.
- ▪Ai Agents In ActionCybersecurityLLMOpen SourceI gave my AI agent one harmless permission.
- ▪It became a backdoor for everyone.Roeehersh5 min read·1 hour ago--ListenShareHow one write path in a helpful bot turned into a permission problem, and the small service I built to close it.Press enter or click to view image in full sizeThe
- ▪You ask it what’s wrong with a service and it comes back in about fifteen seconds with:error rate and latencypod restarts and Kubernetes eventsnode statusthe last pipeline that touched the service, and why it failed if it didA person clicki
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,466 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 | Medium |
| Canonical URL | https://medium.com/@roeehersh/i-gave-my-ai-agent-one-harmless-permission-it-became-a-backdoor-for-everyone-728acf52e37e |
| Publication time | Fri, 25 Sep 2026 17:33:46 +0000 |
| Retrieval time | 2026-09-25T17:45:36.086Z |
| Last seen | 2026-09-25T17:45:36.086Z |
| 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 | -oy6reAb84oD · 1 stories |
| 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
Ai Agents In ActionCybersecurityLLMOpen SourceI gave my AI agent one harmless permission. It became a backdoor for everyone.Roeehersh5 min read·1 hour ago--ListenShareHow one write path in a helpful bot turned into a permission problem, and the small service I built to close it.Press enter or click to view image in full sizeThe agentI built an ops agent at work. You ask it what’s wrong with a service and it comes back in about fifteen seconds with:error rate and latencypod restarts and Kubernetes eventsnode statusthe last pipeline that touched the service, and why it failed if it didA person clicking through dashboards takes ten minutes to get the same picture. The team was using it daily within a week.Reading was safe.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Medium.
Discussion
0 commentsMore from Medium
