nodebench.link_private_signal_to_public_entity
Link an app-private signal to a public entity by hash only. Raw Gmail, resume, inbox, and private artifact text must not be sent.
This record as markdown: /tools/io-github-homenshum-nodebench/nodebench.link-private-signal-to-public-entity.md
What nodebench.link_private_signal_to_public_entity does on Nodebench
AI agents use nodebench.link_private_signal_to_public_entity 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.
Why nodebench.link_private_signal_to_public_entity is rated Medium
This tool creates a linkage (write operation) between a private signal and a public entity using a hash reference. It modifies relational data by establishing a new association. The severity is medium because it could expose sensitive correlations between private signals and public entities if misused, though it explicitly restricts raw private data (Gmail, resume, inbox artifacts) from being sent.
From the tool's definition 'Link an app-private signal to a public entity by hash only' — creates an association/relationship between two entities
Attacks that exploit this kind of access
The rule that runs nodebench.link_private_signal_to_public_entity 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.link_private_signal_to_public_entity, this is the rule to start with:
nodebench.link_private_signal_to_public_entity 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every nodebench.link_private_signal_to_public_entity call is checked against it from then on.
Questions about nodebench.link_private_signal_to_public_entity
Link an app-private signal to a public entity by hash only. Raw Gmail, resume, inbox, and private artifact text must not be sent. 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.
Register the Nodebench MCP server in PolicyLayer and add a rule for nodebench.link_private_signal_to_public_entity: 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.
nodebench.link_private_signal_to_public_entity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the nodebench.link_private_signal_to_public_entity 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.
Set action: deny in the PolicyLayer policy for nodebench.link_private_signal_to_public_entity. 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.
nodebench.link_private_signal_to_public_entity 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.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue