Agno integration

Action security for Agno.

Attach policy to Agno agents, teams and sensitive tools.

Get the Python SDK on PyPITry the local demoRead the documentation

Get the package and source.

Connect the execution boundary.

Attach the firewall to the agent or team and wrap the tools that perform side effects. Test direct tool calls as well as ordinary agent runs.

An example to test

A billing assistant requests a refund to a substituted recipient. Check the sensitive refund tool before it commits the transaction.

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 Agno support.
python -m pip install "agenticdome-python-sdk[agno]"

from agenticdome_sdk.agno import AgenticDomeAgnoFirewall

firewall = AgenticDomeAgnoFirewall()
firewall.attach_firewall(agent_or_team)
secure_tool = firewall.secure_tool(tool_name="billing.refund.issue")(refund_customer)

agenticdome-demo --framework agno --scenario refund_hijack

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.

Read the integration researchUnderstand runtime verification

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.

Try the local demo Book a deployment review