// SCAN REPORT

Pinako AI Bridge

44 tools. 33 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated: 2 Jul 2026

33 can modify or destroy data

11 read-only

44 tools total

Community server · catalogue entry verified 02/07/2026

How to control Pinako AI Bridge ↓

TOOL MAP

What Pinako AI Bridge exposes to your agents

Read (11) Write / Execute (28) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Pinako AI Bridge tools

Destructive · Critical delete_library This tool irreversibly deletes entire libraries and their complete contents across multiple dimensions (tabs, notes, tags, memos, child structures, cloud data). Destructive · High delete_library_group While the default mode (cascadeMembers omitted/false) is reversible (dissolve only), the tool's primary dangerous capability is deletion with cascadeMembers:true, which irreversibly removes owned libraries from cloud and Destructive · High delete_live_node This tool performs irreversible deletion of data structures (tree nodes) and forcibly closes browser tabs. Destructive · High delete_node This tool irreversibly deletes data (node and associated metadata) with no undo mechanism, making it Destructive rather than merely Write.

33 of Pinako AI Bridge's 44 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Pinako AI Bridge

PolicyLayer is an MCP gateway — it sits between your AI agents and Pinako AI Bridge, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_library": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_library_to_group": {
    "limits": [
      {
        "counter": "add_library_to_group_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find_duplicates": {
    "limits": [
      {
        "counter": "find_duplicates_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Pinako AI Bridge — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PINAKO AI BRIDGE →

Instant setup, no code required.

FULL CATALOGUE

All 44 Pinako AI Bridge tools

DESTRUCTIVE 5 tools

Destructive delete_library Permanently deletes a single library and ALL its content (tabs, notes, tags, memos, child windows/groups/folde Destructive delete_library_group Removes a library group. TWO MODES via cascadeMembers: (1) DEFAULT (cascadeMembers omitted/false) — DISSOLVE: Destructive delete_live_node DESTRUCTIVE — closes the live browser tab(s) AND removes the tree node entirely (compound of ghost_node + dele Destructive delete_node DESTRUCTIVE — permanently removes a GHOST node (chromeId=null) and its metadata (tags, memos, star color, cust Destructive delete_note Permanently deletes a note from a library or the main tree. Cloud-side delete is automatic on next persist (th

WRITE 28 tools

Write add_library_to_group Adds an existing library to an existing group. A library can belong to at most one group; rejects with LIBRARY Write add_tags APPENDS tags to a node, deduping and preserving order of existing tags. Use this when the user says Write add_to_bookmarks Inverse direction of add_to_library: clones tree or library nodes INTO the browser\ Write add_to_library Clones TREE nodes (windows, tabs, groups, folders) from a source surface into a library. NOT for library-scope Write bulk_apply Atomically applies up to 250 sub-ops as a SINGLE undoable unit. TWO USE CASES: (1) multi-step reorganizations Write create_folder Creates a new folder node in a library or in the browser bookmarks. NOT for the main tab tree (the main tree u Write create_group Creates a new Pinako group node. Groups can contain other groups and windows but NOT tabs directly (tabs alway Write create_library Creates a new empty library with an auto-seeded Write create_library_group Creates a new library group (an organizational umbrella over multiple libraries). Returns createdGroupId. Afte Write create_note Creates a new note in a library or in the Main Notes. Use this when the user says Write ghost_node Closes the live browser tab(s) for this node and all live descendants, while preserving the tree node with chr Write indent_node Nests a node under its previous sibling (one level deeper). Rejects when the node has no prior sibling (INDENT Write move_node Moves a node (and its full subtree) under newParentId at an optional position. SUBTREE SEMANTICS: all descenda Write outdent_node Promotes a node to its grandparent\ Write remove_library_from_group Removes a library from a group, returning it to the standalone library card list right after the group. The li Write remove_tags Filters specific tags off a node, preserving the rest. No-op for tags not present. Use this for Write reorder_libraries_in_group Reorders the libraries within a single library group. Pass the COMPLETE current list of member library ids in Write reorder_library_panel Reorders the cards in the library panel (standalone library cards + library group cards). Pass the COMPLETE cu Write set_library_description Updates a library\ Write set_library_group_description Updates a library group\ Write set_library_group_title Renames a library group. Trimmed, non-empty, max 200 chars. Write set_library_title Renames a library. Trimmed, non-empty, max 200 chars. THIS IS THE ONLY rename path for libraries — set_title r Write set_memo Sets the memo (short plain-text annotation, max 2500 chars) on a node. Pass empty string to clear. Memos are p Write set_note_content Updates an existing note\ Write set_row_color Sets the rowColor of a Pinako Group node or Folder node. NOT related to Chrome Tab Group color (Chrome owns th Write set_star_color Sets the row star color on a node. Accepts a named color (red, orange, yellow, green, blue, purple) OR its exa Write set_tags REPLACES the entire tag array on a node. Pass an empty array to clear all tags. Use add_tags / remove_tags for Write set_title Sets a custom title on a tab, window, group, or folder node. Trimmed; max 200 chars. Sets customTitle=true so

READ 11 tools

Read find_duplicates Finds exact-URL duplicates within a single scope OR unioned across multiple scopes. Bridge-side scan; no LLM, Read get_bookmarks Returns the user\ Read get_library Returns one library\ Read get_main_tree_notes Returns the Main Notes — rich text documents attached to the user\ Read get_tree Returns the tab tree (Windows → Groups → Tabs) from the Pinako extension. Three legacy modes (prefer composabl Read get_tree_summary Returns a lightweight structural summary of a tree/bookmarks/library WITHOUT returning the actual nodes. Bridg Read list_browsers Lists all Pinako installs currently connected to this MCP server. Each entry: browserBrand (human-readable nam Read list_libraries Lists all Pinako libraries. Default: returns id, title, description, tabCount, and note metadata (id+title onl Read search_docs Searches the Pinako user guide. Returns sections matching the query with title, anchor id, source ( Read search_pinako Omnibus LITERAL substring search across Pinako data surfaces — the broad replacement for search_tabs. Bridge-s Read search_tabs LITERAL substring search across main-tree TAB nodes ONLY (groups, windows, folders, libraries, bookmarks, and

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Pinako AI Bridge

Can an AI agent delete data through the Pinako AI Bridge MCP server? +

Yes. The Pinako AI Bridge server exposes 5 destructive tools including delete_library, delete_library_group, delete_live_node. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Pinako AI Bridge? +

The Pinako AI Bridge server has 28 write tools including add_library_to_group, add_tags, add_to_bookmarks. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Pinako AI Bridge.

How many tools does the Pinako AI Bridge MCP server expose? +

44 tools across 3 categories: Destructive, Read, Write. 11 are read-only. 33 can modify, create, or delete data.

How do I enforce a policy on Pinako AI Bridge? +

Register the Pinako AI Bridge MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Pinako AI Bridge tool call.

Deterministic rules across all 44 Pinako AI Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PINAKO AI BRIDGE →

Instant setup, no code required.

44 Pinako AI Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.