AI agents call find_overlaps to retrieve information from StackSwap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tools | array | Yes | Tool names in the current stack (e.g. ["HubSpot", "Salesforce", "Outreach"]). |
Parameters from the server's own tool schema.
find_overlaps retrieves and queries data from a hand-verified database of tool overlaps. It performs analysis and comparison without side effects, returning information only. This is a classic Read operation: search and lookup functionality with no state changes or irreversible actions.
From the tool's definition Tool description states 'return the redundant pairs' from a curated list and 'savings if one is consolidated' — purely informational query against a static database of overlaps. Server description confirms '8 read-only tools'.
Attacks that exploit this kind of access
Given a list of tool names in a user's stack, return the redundant pairs StackSwap has curated (104 hand-verified overlaps) along with monthly/annual savings if one is consolidated. It is categorised as a Read tool in the StackSwap MCP Server, which means it retrieves data without modifying state.
find_overlaps accepts 1 parameter: tools. Required: tools. The full parameter table on this page comes from the server's own tool schema.
Register the StackSwap MCP server in PolicyLayer and add a rule for find_overlaps: 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 StackSwap. Nothing to install.
find_overlaps 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_overlaps 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_overlaps. 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_overlaps is provided by the StackSwap MCP server (StonesofCreation/stackswap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
find_overlaps is one line of StackSwap's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →