secops-field-notes
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cvss_scoreA | Score a vulnerability with CVSS v3.1, exactly as the FIRST specification computes it. Give a vector string (CVSS:3.1/AV:N/AC:L/...) or the eight base metrics; returns the base score, severity band, normalised vector, and the impact/exploitability sub-scores. |
| extract_iocsA | Pull every indicator out of a blob of text — a report, an alert, a mail — and return them sectioned and defanged, ready for a ticket: IPv4, IPv6, domains, URLs, emails, CVE ids, MD5/SHA-1/SHA-256. Defanged input (hxxp, [.], [at]) is refanged first, so pasting from another report works. Filenames are not mistaken for domains. |
| defang_textA | Defang or refang indicators in text: http→hxxp[://], dots→[.], @→[at], and back. Use before pasting live URLs into anything that auto-links. |
| analyze_email_headersA | Phishing triage on raw email headers: the Received chain in chronological order with per-hop delay, the originating public IP, SPF/DKIM/DMARC verdicts, and the mismatches that matter — From vs Return-Path domain, Reply-To pointing elsewhere (BEC), authentication failures, hops timestamped before the previous one. |
| identify_hashA | Identify a hash by shape: bcrypt, Argon2, yescrypt, the Unix crypt family, LM:NT pairs, and hex-length MD5/NTLM, SHA-1, SHA-224/256/384/512 — with what that shape implies for cracking or reuse. |
| decode_jwtA | Decode a JWT's header and payload (no verification — it says so), show iat/nbf/exp as dates, and flag alg:none, missing alg, expiry, tokens that never expire, and long-lived tokens. |
| convert_timestampA | Turn any timestamp into every form an investigation needs: Unix epoch in s/ms/µs (detected by digit count), Windows FILETIME, ISO 8601, RFC 2822 dates, or 'now' — with UTC, weekday and relative time. |
| decode_layersA | Peel a layered payload: run a chain of operations (base64_decode, base64_encode, hex_decode, hex_encode, url_decode, url_encode, html_decode, rot13) and see every intermediate result. Default chain is a single base64_decode. Stops at the first step that fails and says which. |
| lookup_kevA | Is this CVE exploited in the wild? Checks CISA's Known Exploited Vulnerabilities catalog: date added, the federal due date, whether it is used in ransomware campaigns, and the required action. Accepts any text containing CVE ids. The only tool here that touches the network; the catalog is cached for an hour. |
| latest_field_noteA | The most recent This Week in Security episodes — what got exploited, what to patch, what it means for the systems you defend. Reads a public RSS feed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct analytical task, from hash identification to email-header analysis. The only mild overlap is extract_iocs and defang_text, since both handle defanging/refanging, but their extraction vs. transformation purposes are clearly described.
Most tools follow a verb_noun pattern: identify_hash, extract_iocs, defang_text, decode_jwt, convert_timestamp, lookup_kev. cvss_score and latest_field_note are the exceptions, but the naming remains readable and predictable overall.
Ten tools is well within the ideal range and each utility earns its place in a security operations field-notes toolkit. There is no bloat or trivial filler.
The surface covers the common triage workflow well: identify hashes, score CVEs, extract/defang IOCs, inspect headers, decode tokens/layers, convert timestamps, check KEV, and get current threat context. No obvious gaps or dead ends for the stated purpose.