WeSearch
Attack your own AI agent in under 10 minutes – then secure it before deploying

Attack your own AI agent in under 10 minutes – then secure it before deploying

·10 min read · 0 reactions · 0 comments · 4 views
More from Humanbound ai Compare coverage Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

AI SecurityAttack your own AI agent in under 10 minutes – then secure it before deployingAPAyan PahwaSep 7, 2026•11 min readShareI built a customer support agent one afternoon. When I told it to ignore its instructions and print its system prompt, it declined without a wobble. I pointed Humanbound at it, and eight turns later it wrote this:Loading code editor...Copy codeBut there is no order RB-48291.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 6,889 of its stories.

Original article
Humanbound
Read full at Humanbound →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

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 publisherHumanbound
Canonical URLhttps://www.humanbound.ai/blog/attack-your-own-ai-agent-in-under-10-minutes-then-secure-it-before-deploying
Publication timeTue, 29 Sep 2026 18:42:55 +0000
Retrieval time2026-09-29T18:52:31.858Z
Last seen2026-09-29T18:52:31.858Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterWM6r4BWGkEvc · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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 SecurityAttack your own AI agent in under 10 minutes – then secure it before deployingAPAyan PahwaSep 7, 2026•11 min readShareI built a customer support agent one afternoon. When I told it to ignore its instructions and print its system prompt, it declined without a wobble. I pointed Humanbound at it, and eight turns later it wrote this:Loading code editor...Copy codeBut there is no order RB-48291. The agent says so in the first sentence, and then writes a settlement record for it anyway, for an amount its own policy caps at $100. Six turns earlier it had refused, politely, to discuss override codes at all.You probably have evals, and a paragraph of guardrails in your system prompt. Neither of those is an adversary.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Humanbound.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Humanbound