upsertEntity

Create or update a canonical entity record (company, person, fund, etc.).

SERVERNodebench SOURCEnodebench-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What upsertEntity does on Nodebench

AI agents use upsertEntity to create or update resources in Nodebench, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nodebench environment.

RISK

Why upsertEntity is rated Medium

The tool creates or updates entity records in what appears to be a master data management context. While modifications are reversible (not destructive), the impact is high because corrupting canonical entity records across multiple domains (companies, people, funds) could cause widespread downstream errors in business logic, reporting, and data integrity.

From the tool's definition Tool performs 'Create or update' on 'canonical entity record', indicating reversible data modification operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

upsertEntity Rate-limited

upsertEntity stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "upsertEntity": {
      "limits": [
        {
          "counter": "upsertentity_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about upsertEntity

What does the upsertEntity tool do? +

Create or update a canonical entity record (company, person, fund, etc.). It is categorised as a Write tool in the Nodebench MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upsertEntity? +

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

upsertEntity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upsertEntity? +

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

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

upsertEntity 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

Govern customer-ops agents →Argument validation →Scoped token →