Key facts
| Agent stack | Chat completions, function calling and embeddings are live |
| Use cases | Alert enrichment, IOC summaries, detection rule drafts, incident timelines |
| Least privilege | Read-only tools scoped per integration; no auto-remediation |
| Audit | Log prompts, tool calls, sources and model versions for every run |
| Models | 30+ models; small aliases for classification, stronger ones for synthesis |
| Deployment | Plugsky cloud, your VPC, on-prem and air-gapped options |
| Pricing model | Flat monthly self-serve plans with unlimited fair-use usage |
| Roadmap | Batch and assistants endpoints are coming soon |
TL;DR
- Enrich and prioritise alerts for analysts instead of closing them.
- Summarise indicators and attacker behaviour with cited sources.
- Draft detection rules and incident timelines for human review.
- Never allow autonomous response actions such as blocking or isolation.
- Log every tool call so a security incident can be reconstructed later.
How it works, step by step
- Choose one workflow such as alert enrichment or incident timeline assembly.
- Expose least-privilege, read-only tools for logs, threat intelligence and case systems.
- Ground summaries in retrieved evidence and require source references per claim.
- Draft detection rules and timelines as proposals for analyst review.
- Forbid automated response actions and enforce that in code and network policy.
- Log tool calls and model versions, then measure triage time and false-negative rate.
Try it yourself
Open the AI API key security checklist →
Security workflows suited to agents
Security operations generate more alerts than analysts can read, which is where agents help most:
- Alert enrichment: attach asset context, user history and prior incidents to each alert and rank it.
- IOC summaries: consolidate indicators from multiple sources into a short, cited brief.
- Detection rule drafting: propose rules or queries for an analyst to validate and test.
- Incident timelines: assemble events from logs and notes into a reviewable chronology.
Analysis and response decisions remain with the security team.
Architecture with least privilege
Treat the agent as an untrusted insider and design accordingly:
- Scoped tools: read-only access to logs, intel and case data, with per-integration credentials.
- No response tools: no blocking, isolation, quarantine or credential reset calls.
- Retriever: embeddings over runbooks, prior incidents and detection content.
- Composer: outputs with citations and explicit uncertainty.
- Analyst gate: a human reviews, decides and performs any action.
Rotate tool credentials, cap query scope, and log every call for later forensic review.
Data handling and isolation
Security telemetry can contain personal data, credentials and sensitive infrastructure detail. Redact or reference rather than copying secrets and raw user records into prompts, set retention deliberately, and choose a processing region that satisfies your obligations. Use scoped keys, RBAC, SSO and audit logs across the platform. Where the environment requires it, deploy in a VPC, on-prem or air-gapped setting with the same compatible API, so detections, prompts and evaluations stay portable. Keep the agent out of the critical path: if it is unavailable, alerting and response must continue unchanged.
Pilot and evaluation
Prototype on plugsky-micro or plugsky-lite with historical alerts and a runbook corpus, then use the 14-day full-access trial to test a stronger model on enrichment and timeline building. Measure triage time per alert, ranking quality, citation support and false-negative rate on known incidents. Self-serve plans are flat monthly with fair-use usage, so alert storms do not create variable bills. Roll out to one queue, keep prompts versioned, and re-test whenever data sources or detection content change.
Honest comparison
| Capability | Plugsky | Typical agent framework | Building in-house |
|---|---|---|---|
| Tool calling | Live function calling with per-integration read-only credentials | Framework-specific adapters | You build and maintain |
| Response safety | No auto-remediation; you enforce read-only by design | Varies | You design controls |
| Audit | Log prompts, tool calls and model versions | Partial or add-on | You build all of it |
| Deployment | Cloud, VPC, on-prem and air-gapped | Usually cloud-only | You operate GPUs and serving |
| Pricing | Flat monthly self-serve, fair-use usage | Varies by framework and model | GPU plus operations cost |
Frequently asked questions
Can the agent block or isolate a host?
No. Forbid response actions and keep tools read-only; an analyst decides and performs any remediation through your existing tooling.
Which endpoints do security agents use?
Chat completions, function calling, JSON mode and embeddings are live. Batch and assistants endpoints are coming soon.
How do we keep credentials safe?
Use scoped, rotatable credentials per integration, redact secrets from prompts and logs, and audit every tool call.
Is there a free plan?
Yes. The free plan includes plugsky-micro and plugsky-lite with no credit card, enough to prototype alert enrichment and summarisation.
Can we run it air-gapped?
Yes. Air-gapped deployment is available, and the compatible API means the agent code and evaluations run unchanged.
How does pricing work?
Self-serve plans are flat monthly with unlimited fair-use usage. See the live pricing page for current plans and enterprise options.
How should we measure it?
Track triage time per alert, ranking quality, citation support and false-negative rate against known incidents.