detect_company_mode

Classify a request as own-company, external-company, or mixed-comparison mode before packet routing.

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-company-mode.md

WHAT IT DOES

What detect_company_mode does on Nodebench

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

The tool performs analysis and classification of request modes without executing operations, modifying data, or triggering external side effects. This is a read-like operation that retrieves or categorizes information about a request's type. The severity is low because misuse would only result in incorrect classification, not data loss, code execution, or external damage.

From the tool's definition Tool description states it 'Classify[es] a request' into categorical modes; this is a classification/detection operation with no modification of state or data routing side effects. The tool performs analysis before routing, not the routing itself.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

detect_company_mode Allowed

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

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

FAQ

Questions about detect_company_mode

What does the detect_company_mode tool do? +

Classify a request as own-company, external-company, or mixed-comparison mode before packet routing. 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_company_mode? +

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

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

Can I rate-limit detect_company_mode? +

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

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

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