fsr-agentic-toolkit
Workflows and tools that make an AI agent competent on FortiSOAR. One registry and one safety gate, served three ways: an MCP server, a CLI, and a Python API.
Where it sits
pyfsr SDK: typed REST client, auth, instances. No agent code.
fsr_playbooks Domain: playbook YAML, validation, compile, run analysis.
fsr-agentic-toolkit Agent layer: verbs + seven workflows, MCP server, CLI. <- this repo
products SOC assistant connector, widgets, workshops.
Each layer depends only on the ones above it. The SOC assistant connector can
register the workflows into its own dispatch with
fsr_agentic_toolkit.workflow_tools.register_into_framework(). They stay
hidden from its model until the host opts in.
The seven workflows
| Workflow | Tier | What it returns |
|---|---|---|
orient |
read | Module fields and picklists, read access (and the fix if access is broken), matching connectors |
debug_run |
read | Why a run failed: the failing step, its error, and step args that don't render |
repair_playbook |
read | Mechanical fixes applied to a draft and re-validated; the rest listed |
build_playbook |
read | Facts to draft from, or a gated draft plus the next calls |
verify_effect |
read | What actually changed on a record versus what was expected |
investigate_alert |
read | Alert evidence, indicators, and the enrichment lookups available |
provision_module |
write, confirm | Create, publish, grant roles, then prove read and create work |
Each one returns a WorkflowResult: findings with evidence ids, unknowns, next
steps with their tier, and an id that a follow-up workflow can take.
Use cases compose them. A custom module plus a playbook that acts on it is
provision_module, then build_playbook, then verify_effect.
API only
The toolkit talks to FortiSOAR through its REST API and nothing else. It has
no SSH, shell, log or database tools. Appliance shell tools are a human CLI:
pyfsr appliance ....
Safety
Every call goes through one gate. Writes are tier 2. Destructive tools are
tier 3 and need confirm: true. Environment policy:
FSR_MCP_READONLY=1drops every write.FSR_MCP_ALLOW_TOOLS/FSR_MCP_DENY_TOOLStake comma-separated names.
Install and use
pip install fsr-agentic-toolkit
fsr-agentic-toolkit init --url fortisoar.example.com --api-key <key>
fsr-agentic-toolkit tools
fsr-agentic-toolkit orient --modules alerts --json
fsr-agentic-toolkit debug-run --playbook-or-id "Close Alert"
fsr-agentic-toolkit call search_records '{"module": "alerts", "limit": 5}'
fsr-agentic-toolkit mcp # MCP server on stdio
The box comes from FSR_* environment variables or --instance <alias> from
~/.pyfsr/instances.toml. An explicit FSR_BASE_URL wins over the default
alias.
Development
pip install -e . && pytest
Metadata
Release files for fsr-agentic-toolkit 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| fsr_agentic_toolkit-0.1.0.tar.gz | 110.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fsr_agentic_toolkit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 204.1 kB
Release files / fsr_agentic_toolkit-0.1.0.tar.gz
| Download URL | fsr_agentic_toolkit-0.1.0.tar.gz |
|---|---|
| Size | 110.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4148a947adff7762dfbfbbbad3b5fdd6df6e63b34c8d96cf4b5a72a48960a1e0
|
|
BLAKE2b-256 checksum How to use checksums |
d984d09a7ffd321ca1444260a3175faede22566feaa3081184f03f535c405307
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / fsr_agentic_toolkit-0.1.0-py3-none-any.whl
| Download URL | fsr_agentic_toolkit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 93.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7da330c4ebca4fdacc01e30c49f24361e89c0838e750c569b8d8977a6837d24
|
|
BLAKE2b-256 checksum How to use checksums |
970e1a45b1c6ca53d0bc118b026cfcb609aba62473781878e8fda3a395d05d0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for fsr-agentic-toolkit 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for fsr_agentic_toolkit-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.