How we restrict query agent not to use internet/external search

How we restrict query agent not to use internet/external search. One way could be to via system prompt, is there any specific configuration available for that?

Hey @waseem_sarwar ,

Welcome to our community, it’s lovely to have you here :smiling_face_with_three_hearts:

I can see you’re asking about Query Agent, which means you’re on our Cloud. Since you are, I would suggest opening a ticket with us at support@weaviate.io, as we have a workflow process and fast responses for our Cloud customers.

However, just to also give you brief, Weaviate Query Agent is a pre-built agentic service that operates exclusively on data stored in your Weaviate Cloud collections, it does not have built-in internet or external search capabilities.

The Query Agent’s workflow is:

  • Analyze the user’s natural language query
  • Perform searches against your specified Weaviate collections
  • Generate a response based on those results

In summary, the Weaviate Query Agent does not perform internet searches by design, it only queries your Weaviate Cloud data.

Best regards,
Mohamed Shahin
Weaviate Admin, Support Engineer
(Ireland, UTC±00:00/+01:00)

1 Like

Thanks @Mohamed_Shahin !

I would reach via support@weaviate.io since we have been observing the information provided by the query agent is not grounded to the RAG, many times it gives us the data which doesn’t exist in the queried collections, however exists publicly on the internet.

@waseem_sarwar Yes please, I will confirm further from our Lab team in case. The agent only uses Weaviate cluster and LLM. It decides how to retrieve results from your Weaviate cluster and then sends them to LLM to generate an answer.

Please open a ticket and let’s try figure it out together in case it needs improvement.

Best regards,
Mohamed Shahin
Weaviate Admin, Support Engineer
(Ireland, UTC±00:00/+01:00)