share_revoke_packet_link

Revoke a local share link so it no longer counts as active.

SERVERNodebench SOURCEnodebench-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/share-revoke-packet-link.md

WHAT IT DOES

What share_revoke_packet_link does on Nodebench

AI agents call share_revoke_packet_link to permanently remove resources in Nodebench, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why share_revoke_packet_link is rated Critical

Revoking a share link is an irreversible action that deactivates access for anyone using that link. Once revoked, the link cannot be un-revoked (at least not automatically), making this a destructive operation. The blast radius is medium since it affects link-based access rather than underlying data.

From the tool's definition Revoke a local share link so it no longer counts as active

Attacks that exploit this kind of access

RECOMMENDED RULE

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

share_revoke_packet_link Hidden

share_revoke_packet_link is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "share_revoke_packet_link"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about share_revoke_packet_link

What does the share_revoke_packet_link tool do? +

Revoke a local share link so it no longer counts as active. It is categorised as a Destructive tool in the Nodebench MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on share_revoke_packet_link? +

Register the Nodebench MCP server in PolicyLayer and add a rule for share_revoke_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.

What risk level is share_revoke_packet_link? +

share_revoke_packet_link is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit share_revoke_packet_link? +

Yes. Add a rate_limit block to the share_revoke_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.

How do I block share_revoke_packet_link completely? +

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

What MCP server provides share_revoke_packet_link? +

share_revoke_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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools → Critical-risk tools on this server →

Across the catalogue

web3_revoke_key on 0xarchive →revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →