Finds exact-URL duplicates within a single scope OR unioned across multiple scopes. Bridge-side scan; no LLM, no agent reasoning required. For v1 ships with exact URL match only — byte-identical URLs grouped together; URLs differing in tracking params (utm_source, fbclid, etc.) or fragment identi...
AI agents call find_duplicates to retrieve information from Pinako AI Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves bookmark/library data to find duplicates, which is a non-destructive read operation. It has no side effects—it does not modify, delete, or execute any external actions. The low severity reflects minimal risk even if misused, as it merely scans and reports information without altering state or triggering external operations.
From the tool's definition The tool 'finds exact-URL duplicates within a single scope OR unioned across multiple scopes' and performs a 'Bridge-side scan' with no side effects.
Attacks that exploit this kind of access
Finds exact-URL duplicates within a single scope OR unioned across multiple scopes. Bridge-side scan; no LLM, no agent reasoning required. For v1 ships with exact URL match only — byte-identical URLs grouped together; URLs differing in tracking params (utm_source, fbclid, etc.) or fragment identifiers are treated as DISTINCT. Fuzzy / near-duplicate matching deferred to v2 polish.\n\n. It is categorised as a Read tool in the Pinako AI Bridge MCP Server, which means it retrieves data without modifying state.
Register the Pinako AI Bridge MCP server in PolicyLayer and add a rule for find_duplicates: 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 Pinako AI Bridge. Nothing to install.
find_duplicates 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 find_duplicates 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 find_duplicates. 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.
find_duplicates is provided by the Pinako AI Bridge MCP server (teleomorph/pinako-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →