detect_vertical

Detect the founder vertical and subvertical from the query and context.

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/detect-vertical.md

WHAT IT DOES

What detect_vertical does on Nodebench

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

This tool analyzes and retrieves classification information (founder vertical/subvertical) from provided query and context parameters. It performs pattern matching or categorization on input data to return results, which is a read-only operation with no state changes, data modifications, or external side effects.

From the tool's definition Tool name is 'detect_vertical' and description states it 'Detect[s] the founder vertical and subvertical from the query and context.' The verb 'detect' indicates information retrieval/analysis of existing data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

detect_vertical Allowed

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

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

FAQ

Questions about detect_vertical

What does the detect_vertical tool do? +

Detect the founder vertical and subvertical from the query and context. 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 detect_vertical? +

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

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

Can I rate-limit detect_vertical? +

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

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

detect_vertical 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

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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