greynoise-mcp-server

Official

by GreyNoise-Intelligence

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get Blocklist

get-blocklist

Read-only

Retrieve a blocklist's configuration by ID to inspect its settings, with an optional workspace ID to target a specific workspace.

Instructions

Retrieve a single blocklist's configuration by ID.

Input Schema

Name	Required	Description	Default
`blocklist_id`	Yes	Blocklist ID (UUID)
`workspace_id`	No	Workspace ID (UUID). Defaults to the workspace the API key is bound to.

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	No
`query`	No
`token`	No
`enabled`	No
`ip_limit`	No
`created_at`	No
`updated_at`	No
`workspace_id`	No
`last_ip_count`	No
`entitlement_level`	No
`query_workspace_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.5.5Nov 2, 2026

removedOutput schema / properties / ip_limit / anyOf

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

addedOutput schema / properties / ip_limit / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / name / anyOf

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

addedOutput schema / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Addedv0.5.4Jul 23, 2026

TDQS

A3.6/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 the safety profile is covered and nothing contradicts it. The description adds only one useful nuance — 'configuration' signals it returns the blocklist's settings rather than its IP entries — but says nothing about auth, scoping, or missing-record behavior.

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

Conciseness5/5

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

One sentence, front-loaded with the action and resource, with zero filler. Sized appropriately for a simple single-record getter.

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

Completeness4/5

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

The tool is simple, fully documented parameters, and an output schema exists, so return values need not be explained. The only shortfall is that an agent must infer the boundary with get-blocklist-ips and list-blocklists.

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% and both parameters (blocklist_id, workspace_id) are documented, including the workspace defaulting rule. The description only restates 'by ID' and adds no syntax or scoping detail beyond the schema, so baseline 3 applies.

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?

Specific verb+resource ('Retrieve a single blocklist's configuration by ID'), and the word 'single' implicitly separates it from list-blocklists and get-blocklist-ips. It stops short of naming those siblings, so differentiation is left partly to inference.

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 'by ID' framing implies this is for fetching a known blocklist, but there is no explicit when-to-use versus list-blocklists (browse) or get-blocklist-ips (the entries themselves). No prerequisites or exclusions are stated.

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

Deploy Server