> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/datalogz-mcp-servers/datalogz-control-tower-mcp-faq.md).

# Datalogz Control Tower MCP FAQ

**Does my assistant see the contents of our reports?**\
No. It sees metadata: names, types, owners, workspaces, refresh outcomes, usage counts, access roles, similarity scores and lineage edges. It does not see the rows inside a dataset, the visuals on a page, or the results of a query.

**Can it change anything in Control Tower or in Power BI?**\
No. Every tool is read-only. See What this server will not do.

**Will the numbers match what the app shows?**\
Yes. It reads the same warehouse, so figures reconcile with BI360, Inventory and Alerts, and are as fresh as your last connector scan.

**Can someone ask about a connector they are not entitled to?**\
No. Every query is scoped to the calling credential, using the same permission model as the app.

**Do I need to know the tool names?**\
No. Ask in plain language and a connected assistant picks the tools. Common questions shows the sequences if you want to check the route it took.

**Does it work for platforms other than Power BI?**\
Yes, with narrower coverage. Inventory, alerts and refresh health work everywhere. Usage, viewers, workspace access and capacity state are Power BI only.

**Is it safe to let a wider team use it?**\
It is read-only, and each person's credential scopes what they can reach. Treat responses the way you treat exports from the app, since usage and access tools return names and email addresses. See Datalogz Security.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.datalogz.io/guides/datalogz-mcp-servers/datalogz-control-tower-mcp-faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.