# Handling tool failures

Capture the tool name, inputs, error code, and timestamp; check permissions and connectivity, correct one cause, then repeat the smallest failing call.

![Handling tool failures in Foxora v5.0.3](/docs/images/v5.0.3/studio/tools-overview.webp)

## Where this lives

Open **studio → Tools**.

Tools are typed capabilities that let an agent inspect or change files, run commands, browse, control applications, query services, or call connected integrations.

> **Safety:** Tool output is untrusted data and can contain misleading instructions. Do not grant a tool broader filesystem, account, or network access merely to avoid configuration work.

## Steps

1. Open **studio → Tools**.
2. Reproduce the problem once with the smallest safe input and record the exact message, action, and time.
3. Capture the tool name, inputs, error code, and timestamp.
4. Check permissions and connectivity.
5. Correct one cause.
6. Repeat the smallest failing call.
7. Change one reversible condition, then repeat the same test. Preserve logs or exports before any reset.
8. **Confirm the result.** Run one representative call, inspect the structured result or error, and confirm the underlying file, process, page, application, or external service changed as intended.

## Choose the right path

- Use built-in tools for local and first-party capabilities.
- Use Composio-managed plugins for supported SaaS integrations.
- Use MCP for a custom or organization-provided tool server.


## Confirm it worked

- Run one representative call, inspect the structured result or error, and confirm the underlying file, process, page, application, or external service changed as intended.
- The screen, command, file, run, or destination named in this guide reflects the expected state.