share_create_packet_link
Create a durable local share link record for a packet or founder memo so it can be rendered or synced later.
This record as markdown: /tools/io-github-homenshum-nodebench/share-create-packet-link.md
What share_create_packet_link does on Nodebench
AI agents use share_create_packet_link 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 share_create_packet_link is rated Medium
This tool creates a shareable link record for content (packets or founder memos), which is a reversible write operation—the record can be modified or deleted later. It doesn't execute arbitrary code, move financial data, or irreversibly destroy information. The 'durable' qualifier suggests persistent storage, but the operation itself is creating (Write), not executing or destructive.
From the tool's definition The tool description states 'Create a durable local share link record', which indicates it creates and persists a new data structure. The verb 'create' combined with 'record' demonstrates a write operation that generates new data.
Attacks that exploit this kind of access
The rule that runs share_create_packet_link 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 share_create_packet_link, this is the rule to start with:
share_create_packet_link 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 share_create_packet_link call is checked against it from then on.
Questions about share_create_packet_link
Create a durable local share link record for a packet or founder memo so it can be rendered or synced later. 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 share_create_packet_link: 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.
share_create_packet_link 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 share_create_packet_link 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 share_create_packet_link. 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.
share_create_packet_link 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