enrich_recon

Retroactively enrich an existing recon session with live web search results. Call this after run_recon when you

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/enrich-recon.md

WHAT IT DOES

What enrich_recon does on Nodebench

AI agents call enrich_recon 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 enrich_recon is rated Low

This tool performs a read operation by retrieving live web search results to augment an existing recon session. There is no indication it modifies, deletes, or executes arbitrary code—it simply fetches and enriches data, which is characteristic of a Read category tool. Low severity because web search data retrieval has minimal blast radius.

From the tool's definition Tool name is 'enrich_recon' and description indicates it enriches 'with live web search results'. The verb 'enrich' combined with 'search results' indicates data retrieval.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs enrich_recon 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 enrich_recon, this is the rule to start with:

enrich_recon Allowed

enrich_recon 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": {
    "enrich_recon": {}
  }
}

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 enrich_recon call is checked against it from then on.

FAQ

Questions about enrich_recon

What does the enrich_recon tool do? +

Retroactively enrich an existing recon session with live web search results. Call this after run_recon when you. 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 enrich_recon? +

Register the Nodebench MCP server in PolicyLayer and add a rule for enrich_recon: 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 enrich_recon? +

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

Can I rate-limit enrich_recon? +

Yes. Add a rate_limit block to the enrich_recon 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 enrich_recon completely? +

Set action: deny in the PolicyLayer policy for enrich_recon. 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 enrich_recon? +

enrich_recon 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 →