Critical Risk →

lib_share

Manage project sharing permissions. Share projects with other users by email, list existing shares, or revoke access. - share: Grant access to a user (requires user_email and permission_level) - list: List all users with access to a project - revoke: Remove a user's access (requires user_id_to_r...

Bulk/mass operation — affects multiple targets

Part of the Soundside-ai MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call lib_share to permanently remove or destroy resources in Soundside-ai. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call lib_share in a loop, permanently destroying resources in Soundside-ai. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

kangaroo-ifly-soundside-ai.yaml
tools:
  lib_share:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Soundside-ai policy for all 12 tools.

Tool Name lib_share
Category Destructive
Risk Level Critical

View all 12 tools →

Agents calling destructive-class tools like lib_share have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

lib_share is one of the critical-risk operations in Soundside-ai. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the lib_share tool do? +

Manage project sharing permissions. Share projects with other users by email, list existing shares, or revoke access. - share: Grant access to a user (requires user_email and permission_level) - list: List all users with access to a project - revoke: Remove a user's access (requires user_id_to_revoke). It is categorised as a Destructive tool in the Soundside-ai 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 lib_share? +

Add a rule in your Intercept YAML policy under the tools section for lib_share. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Soundside-ai MCP server.

What risk level is lib_share? +

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

Yes. Add a rate_limit block to the lib_share rule in your Intercept 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 lib_share completely? +

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

lib_share is provided by the Soundside-ai MCP server (kangaroo-Ifly/soundside-ai). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.