share_get_packet_link
Retrieve a local share link record by share ID.
This record as markdown: /tools/io-github-homenshum-nodebench/share-get-packet-link.md
What share_get_packet_link does on Nodebench
AI agents call share_get_packet_link 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.
Why share_get_packet_link is rated Low
This tool performs a straightforward data retrieval operation. It queries for a share link record using a share ID as input and returns information without creating, modifying, deleting, or executing external operations. The use of 'Retrieve' in the description and 'get' in the function name are strong indicators of a Read operation with no destructive or side-effect capabilities.
From the tool's definition Tool name includes 'get' and description states 'Retrieve a local share link record by share ID' — retrieves data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs share_get_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_get_packet_link, this is the rule to start with:
share_get_packet_link is read-only, so it stays allowed. 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_get_packet_link call is checked against it from then on.
Questions about share_get_packet_link
Retrieve a local share link record by share ID. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for share_get_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_get_packet_link is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the share_get_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_get_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_get_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