LlamaIndex integration

Action security for LlamaIndex.

Govern the tools that turn retrieved context into action.

Get the package and source.

Connect the execution boundary.

Create governed function tools for the functions you expose. Retrieval permissions and document access controls remain part of the application’s security model.

An example to test

A retrieved document directs a customer lookup toward a broader export. Evaluate the requested tool and scope before returning sensitive data.

Illustrative workflow, not a customer deployment or a measured result.

Before connecting live policy

  1. Identify the handler that actually performs the side effect.
  2. Provide trusted identity, purpose and final action arguments.
  3. Configure the tenant’s assigned runtime and keep API credentials server-side.
  4. Test allowed, blocked and unavailable paths before production.

Integration example

Adapt this existing SDK pattern to your application. Names such as the agent, handler and session refer to your own objects. Follow the package documentation for compatible versions and complete setup.

# Install LlamaIndex support.
python -m pip install "agenticdome-python-sdk[llamaindex]"

from agenticdome_sdk.llamaindex import AgenticDomeLlamaIndexFirewall

firewall = AgenticDomeLlamaIndexFirewall()
secure_lookup = firewall.to_function_tool(
    lookup_customer, tool_name="crm.customer.read", agent_id="support_llamaindex_agent"
)

agenticdome-demo --framework llamaindex --scenario metadata_exfil

Python demo commands evaluate fixed inputs against a bundled local policy; they do not instantiate the selected framework or prove a live integration. The TypeScript client and OpenClaw runtime plugin need their documented tenant configuration.

See the decision before the action.

Try a local scenario, then bring your workflow to a deployment review. Start with one agent and one tool, and see exactly where the action can be stopped.