generate_share_token

Generate a temporary public URL for a private file — perfect for sharing previews without making the file permanently public. Returns

SERVEREasyBits SOURCE@easybits.cloud/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/generate-share-token.md

WHAT IT DOES

What generate_share_token does on EasyBits

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

RISK

Why generate_share_token is rated Critical

An AI agent that decides to call generate_share_token doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from EasyBits is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs generate_share_token safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_share_token, this is the rule to start with:

generate_share_token Hidden

generate_share_token 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": [
    "generate_share_token"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about generate_share_token

What does the generate_share_token tool do? +

Generate a temporary public URL for a private file — perfect for sharing previews without making the file permanently public. Returns. It is categorised as a Destructive tool in the EasyBits 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 generate_share_token? +

Register the EasyBits MCP server in PolicyLayer and add a rule for generate_share_token: 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 EasyBits. Nothing to install.

What risk level is generate_share_token? +

generate_share_token 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 generate_share_token? +

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

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

generate_share_token is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern infrastructure agents →Blast radius →Tool call approval →