greynoise-mcp-server

Official

by GreyNoise-Intelligence

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get Session

get-session

Read-only

Retrieve full metadata and connection details for a single GreyNoise sensor session by ID, including IPs, ports, timestamps, byte and packet counts, classification, and enrichment fields.

Instructions

Get full metadata and connection details for a single GreyNoise sensor session by its ID. Returns source/destination IPs and ports, timestamps, byte/packet counts, classification, and any additional enrichment fields.

Input Schema

Name	Required	Description	Default
`scope`	No	Data scope for the query (default: workspace)
`session_id`	Yes	The unique session identifier

Output Schema

Name	Required	Description	Default
`id`	No
`_id`	No
`source`	No
`lastPacket`	No
`destination`	No
`firstPacket`	No
`classification`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.5.5Nov 2, 2026

removedOutput schema / properties / firstPacket / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]

addedOutput schema / properties / firstPacket / type
```
Added value: +[
+  "string",
+  "number"
+]
```

removedOutput schema / properties / lastPacket / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]

addedOutput schema / properties / lastPacket / type
```
Added value: +[
+  "string",
+  "number"
+]
```

Changed2 schema fields changedv0.5.3Jul 21, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "_id": {
+      "type": "string"
+    },
+    "classification": {
+      "type": "string"
+    },
+    "destination": {
+      "additionalProperties": {},
+      "properties": {
+        "bytes": {
+          "type": "number"
+        },
+        "ip": {
+          "type": "string"
+        },
+        "packets": {
+          "type": "number"
+        },
+        "port": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "firstPacket": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        }
+      ]
+    },
+    "id": {
+      "type": "string"
+    },
+    "lastPacket": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        }
+      ]
+    },
+    "source": {
+      "additionalProperties": {},
+      "properties": {
+        "bytes": {
+          "type": "number"
+        },
+        "ip": {
+          "type": "string"
+        },
+        "packets": {
+          "type": "number"
+        },
+        "port": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedv0.4.0Jun 14, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety behavior is covered and the description's only added context is that it targets one session and touches external GreyNoise data. It says nothing about permissions, missing-ID behavior, or rate limits beyond the annotation. It also spends its behavioral budget restating return fields that the output schema already defines.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, action-first, with the identifying constraint in the opening clause. The second sentence is largely a restatement of the output schema, so one sentence does not fully earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-record read with a rich output schema and read-only annotations, this is adequate, but the unmentioned optional scope parameter and the redundant return-field enumeration leave the definition slightly misallocated. An agent knows how to call it but not how the scope parameter changes the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented, and the description only echoes the required session_id. The optional 'scope' parameter and its 'default: workspace' behavior are never mentioned in the description, so no meaning is added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Get full metadata and connection details for a single GreyNoise sensor session by its ID') and scopes it to one record, which implicitly separates it from search-sessions and the aggregation siblings. It stops short of explicitly contrasting with session-connections or session-fields, whose names overlap with the 'connection details' claim.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'a single ... session by its ID' implies this is the retrieval path when you already hold an identifier, versus the search/list siblings, but the description never states when to use it over alternatives such as search-sessions or session-fields. Use context is inferred rather than instructed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server