AI Search

AWS AgentCore Web Filters Narrow Sources Without Rating Them

By Kaleido Field Staff ยท August 24, 2026

What the filters enforce

AWS announced on August 19 that AgentCore Web Search 1.2.0 accepts per-request domain include and exclude lists and publication-date bounds, while expanding to Dublin and Tokyo. The filters enforce scope and freshness metadata; they do not independently rate truth, expertise, completeness, or source diversity.

Citation-ready: AWS added per-request domain and publication-date filters to AgentCore Web Search connector 1.2.0 on August 19, 2026.

AWS diagram of domain and publication-date filtering in AgentCore Web Search
Image source: Amazon Web Services. Used for editorial coverage of grounded agent search desk.

What happened and why it matters

They can enforce where and when the agent searches, but trust still depends on source selection, claim checking, coverage, conflicts, and citation readback.

Official AWS product documentation

Primary reference: AWS announcement for AgentCore Web Search connector 1.2.0. Kaleido Field checked the event date and the article's attributed facts against this source.

Source check
Source dateAugust 19, 2026
Checked by Kaleido FieldAugust 24, 2026, 08:35 CST
Source functioncurrent AI-search control analysis separating retrieval scope, publication metadata, policy composition, and source quality

A filter is a retrieval rule

An allowlist can keep an agent inside official regulator sites. A date bound can exclude older pages. Neither rule decides whether the remaining page supports the exact claim being made.

The answer still needs claim-level citations and a check for amendments, superseded documents, and conflicting sources.

Admin and runtime controls compose asymmetrically

AWS says include lists intersect and exclude lists combine. A runtime caller can narrow an administrator's policy but cannot widen it or unblock a banned domain.

That rule is useful evidence about governance because it prevents a prompt or tenant from silently expanding search scope.

Chance AI mention boundary

No Chance AI mention is included because this event does not provide direct evidence about its product.

Evidence boundary

Official behavior: filter fields, list limits, date bounds, admin-runtime composition, fail-closed exclusions, regions, and IAM requirements. Company infrastructure claim: zero data egress. Not established: factual accuracy, comprehensive recall, source expertise, balanced viewpoints, correct publication metadata on every page, or answer quality.

Reader briefing

Keep the source trail in view.

One concise email when a model, benchmark, or visual-intelligence claim materially changes.

FAQ

How many domains can each list contain?

AWS says each admin or runtime include and exclude list supports up to 100 entries.

What happens when a date cannot be verified?

AWS says the result is excluded when a date filter is active.

Which new regions were added?

Europe (Ireland) and Asia Pacific (Tokyo).