> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/guardian/workspace/tools.md).

# Tools

Tools are reusable policy components for specialized policy logic. They encapsulate blocks, events, and schemas behind a defined external interface.

Use tools to standardize a capability across policies. A policy references a tool without exposing its internal implementation.

### The problem tools solve

Tools keep reusable logic consistent across policy implementations. They also protect the tool's internal blocks, events, and schemas from unintended changes.

### How tools work

Tools expose variables and input or output events. Policies use these interfaces to provide configuration and exchange data with the tool.

Tool schemas are embedded within the tool. A policy can use those schemas when it includes the tool.

Tools can contain other tools. This supports layered implementations for complex methodologies.

### Key distinctions

Tools and modules both encapsulate reusable policy logic. Tools remain isolated and are referenced by policies. Their internal implementation is not directly editable from the policy using them.

Published tools are immutable. Standard Registries can configure only the tool's exposed interfaces.

### Related

* Reference: [Tools Reference](/docs/develop/guardian/workspace/tools/tools-using-ui.md)
* Concept: [Modules](/docs/develop/guardian/workspace/modules.md)
* Concept: [Policy Configurator](/docs/develop/guardian/workspace/policies/policy-creation/policy-configurator.md)


---

# 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://guardian.hedera.com/docs/develop/guardian/workspace/tools.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.