> For the complete documentation index, see [llms.txt](https://docs.mosofin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosofin.com/product-guide/flow-settings.md).

# API Tools

API Tools is the workspace's permission center for financial data reads. Use it to decide which tools an agent can call for a connected source.

## Read the page

The data-source rail identifies the selected connection. The main panel shows its connection status, owning agent, tool counts, and the policy for each tool.

Policies have three levels:

| Policy                 | Meaning                                                             |
| ---------------------- | ------------------------------------------------------------------- |
| **Enabled**            | The agent can call the read-only tool without pausing for approval. |
| **Require permission** | The request must be approved before the tool runs.                  |
| **Disabled**           | The tool is unavailable to the agent.                               |

## Change a policy

1. Select the financial data source.
2. Find the tool you want to govern.
3. Choose **Enabled**, **Ask**, or **Off** in the segmented control.
4. Confirm that the status badge and summary counts update.

Policy changes are owner-governed and are recorded in activity history. If a control is unavailable, confirm that you have the required role and that the data source is connected.

## Choose an appropriate level

Use **Enabled** for routine, low-risk reports your team relies on. Use **Require permission** for sensitive reads or when you want a human checkpoint. Use **Disabled** when the workspace should never expose that capability.

> **Note:** These controls govern access to read-only MosoFin tools. Enabling a tool does not grant permission to write transactions back to the connected accounting system.


---

# 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.mosofin.com/product-guide/flow-settings.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.