> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/user-documentation/blue-enzyme-vaults/vault-settings/interactive-blocks.md).

# Operations Control

{% hint style="info" %}
The policies on this page help keep Asset Managers within your vault's mandate and limit the impact of mistakes. Asset Managers are fully trusted, so these policies are operational guardrails, not protection against a malicious or compromised Asset Manager. See Delegation.
{% endhint %}

### Allowlist

Vault owners are able to create and edit lists of integrations (adapters and/or external positions). This restricts which integrations a permissioned trader can access via the vault.

#### Allowed adapters

Adapters are integrations which enable you to interact with various DeFi protocols. An Adapter is terminology we use to signal that interacting with this DeFi integration is being represented by a liquid, divisible, fungible token.

Enabling this policy means that your vault will only be able to interact with DeFi adapter integrations that you select. Importantly, restricting your vault to only have adapter connectivity will reduce trust assumptions and give it a superior liquidity properties.

#### Allowed external positions

An external position is similar to an adapter integration in that it allows you to interact with external DeFi protocols. However, they differ in that they are not represented by a liquid, divisible, fungible token (eg. Compound CDPs or Uniswap v3 LP positions, Maple Lending, Aave Borrowing and Convex Voting). This policy defines which external position “types” can the vault interact with. Selecting external positions on this policy means that your vault will only be able to interact with external positions on this list.

Note that if a vault is able to interact with external positions, it increases trust assumptions and introduces the potential for some risks.

#### Asset disallowed list

An asset disallowed list enables a vault owner to specify assets from the asset universe which are "off limits". Nobody can trade these assets from within the vault whilst they are on this list. This is a useful policy to use if you want to disallow assets with low quality price feeds being held in the vault. This can lead to inaccurate NAV pricing and possible arbitrage risk.

### Slippage stop-loss

This policy is designed to limit accidental actions (e.g., poorly executed trades or misconfigured routes) which could cause a loss to the value of the vault.

It does this by limiting the value loss (i.e. slippage) that can occur via adapter actions over a “tolerance period” (a rolling 7 day period).

Vault owners can define a tolerance threshold (eg. 10%).

Whenever an adapter action results in slippage, that slippage amount is added to a cumulative slippage total. The accumulated slippage then diminishes over the “tolerance period duration” at a constant rate based on the fund’s chosen tolerance. This policy allows bypassing the slippage checks entirely if the adapter being called is in a Council-maintained list on the AddressListRegistry (adapters whose actions cannot be routed to leak vault value).

### Restrict asset position removal

This policy exists to prevent an asset from being un-tracked in the vault while it still holds significant value, such that it is no longer being accounted for. This can create incorrect valuation of vaults.

The policy prevents the removal of an asset from the vault's accounting unless a) it does not have a valid price, or b) its value can be considered negligible (i.e. dust). The dust threshold is maintained by the Enzyme Council.

### Restrict external position removal

This policy exists to prevent an external position from being removed from the vault while it still holds significant value, such that it is no longer being accounted for. This can create incorrect valuation of vaults.

This policy prevents the removal of an external position from the vault’s accounting unless its value can be considered negligible (i.e. dust). The dust threshold is maintained by the Enzyme Council.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.enzyme.finance/user-documentation/blue-enzyme-vaults/vault-settings/interactive-blocks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
