AWS has added domain and publish-date filtering to the Web Search tool inside Amazon Bedrock AgentCore, according to the AWS Machine Learning Blog. AgentCore is AWS's managed runtime for building and running AI agents, and its Web Search tool lets those agents fetch live information from the internet rather than relying solely on a model's training data or a fixed knowledge base.
The new filters let developers constrain a search to a specified list of domains and set a recency window, so results outside the allow-list or older than the cutoff are excluded before they ever reach the agent's reasoning step. AWS frames this as a way to improve both relevance and trust: an agent answering a support question can be restricted to a company's own help center plus a short list of vetted vendor sites, and a research agent can be told to ignore anything published before a given date.
This is a narrow but practical change. Open-ended web search grounding has been one of the harder problems for teams deploying customer-facing or internal AI agents, because the model has no inherent way to judge source quality or currency — it will happily cite a stale forum post with the same confidence as an authoritative source. Domain and date filters push that judgment upstream, into a configuration a builder controls directly, rather than leaving it to prompt instructions the model may or may not follow.
For operations teams, the change matters most in three places: customer support agents that need to cite only company-approved documentation, sales or research agents that need current pricing or competitive information rather than dated pages, and any workflow with a compliance requirement to show which sources an AI system was allowed to draw from. Restricting the source pool also narrows the attack surface for prompt injection via malicious web content, since fewer, known domains are reachable.
The feature is specific to AgentCore's Web Search tool and does not change how other retrieval methods, such as vector databases or internal knowledge bases, behave. Teams already running agents on AgentCore with web search enabled can apply the filters through the tool's configuration; AWS's post does not specify pricing changes tied to the update, so cost impact should be treated as unconfirmed pending direct testing.