# Agents Accessing Each Other's Knowledge Sources Despite Explicit Scoping

**URL:** <https://community.crewai.com/t/agents-accessing-each-others-knowledge-sources-despite-explicit-scoping/6666>\
**Category:** CrewAI Community Support\
**Tags:** agent\
**Created:** [July 24, 2025, 6:20am UTC](https://community.crewai.com/t/agents-accessing-each-others-knowledge-sources-despite-explicit-scoping/6666 "2025-07-24T06:20:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gary\_Frewin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.crewai.com/gary_frewin/32/4135_2.png) [@Gary\_Frewin](https://community.crewai.com/u/Gary_Frewin)\
**Post date:** [July 24, 2025, 6:20am UTC](https://community.crewai.com/t/agents-accessing-each-others-knowledge-sources-despite-explicit-scoping/6666/1 "2025-07-24T06:20:24Z")

</div>

Hi everyone,

I’m running into what seems like a bug or a misunderstanding around how `knowledge_sources` are scoped per agent. According to [CrewAI documentation on knowledge](https://docs.crewai.com/en/concepts/knowledge), each agent should only access the knowledge sources explicitly assigned to it.

### ✅ What I Expect:

Each agent has a different domain (e.g., climbing, to-dos, finance) and is passed its own isolated knowledge sources like this:

```auto
Agent(
  config=...,
  knowledge_sources=[climbing_txts, climbing_jsons],
  llm=self.llm
)

```

And similarly for other agents. I do **not** pass any `knowledge_sources` at the crew level.

### ❌ What Actually Happens:

When the crew runs, agents seem to access all knowledge, even sources not assigned to them. For example:

- My `climbing_task_proposer` agent retrieves tasks from `todo/tasks.json`, even though it was never given access to it.
- This happens even with clearly separated file paths and agent logic.
- Every agent seems to have access to everything in the `knowledge` folder.

### 🔍 Debug Info:

- I’m seeing log output like:

bash

CopyEdit

```auto
Retrieved Knowledge:
todo/tasks.json...

```

…while executing a climbing-only agent task.

### ❓Questions:

- Is this a known issue in CrewAI?
- Is agent-specific knowledge currently functioning as intended?
- Any workaround to **strictly isolate agent knowledge**?

Would love insight from anyone who’s worked through this

Thanks in advance 🙏