nodebench.dossiers.get

Get a sourced public dossier for an entity by entity ID, key, name, or domain.

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/nodebench.dossiers.get.md

WHAT IT DOES

What nodebench.dossiers.get does on Nodebench

AI agents call nodebench.dossiers.get to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why nodebench.dossiers.get is rated Low

This tool retrieves or queries existing dossier data by entity identifier without side effects. It is a straightforward data retrieval operation returning public information, consistent with the Read category. The 'public' qualifier and retrieval-only nature further support low severity.

From the tool's definition Tool name contains 'get'; description states 'Get a sourced public dossier' which retrieves data about an entity. No modification, deletion, or execution of external operations mentioned.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nodebench.dossiers.get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nodebench.dossiers.get, this is the rule to start with:

nodebench.dossiers.get Allowed

nodebench.dossiers.get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nodebench.dossiers.get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every nodebench.dossiers.get call is checked against it from then on.

FAQ

Questions about nodebench.dossiers.get

What does the nodebench.dossiers.get tool do? +

Get a sourced public dossier for an entity by entity ID, key, name, or domain. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on nodebench.dossiers.get? +

Register the Nodebench MCP server in PolicyLayer and add a rule for nodebench.dossiers.get: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Nodebench. Nothing to install.

What risk level is nodebench.dossiers.get? +

nodebench.dossiers.get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nodebench.dossiers.get? +

Yes. Add a rate_limit block to the nodebench.dossiers.get rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block nodebench.dossiers.get completely? +

Set action: deny in the PolicyLayer policy for nodebench.dossiers.get. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides nodebench.dossiers.get? +

nodebench.dossiers.get is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →