Run a preview StackScan: pass a list of tools + team size + industry, get back current spend, optimized spend, monthly/annual recoverable, headless gaps (tools with no MCP/API connection an owned head can call), and the top 5 replace/remove opportunities. Includes a link to the full paid audit on...
AI agents call scan_stack 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 user's current stack. |
industry | string | — | Industry slug or label. Recognised slugs: b2b_saas, revenue_sales_tech, marketing_tech, revops_operations, real_estate_tech, fintech_financial, dev_tools_plg, h |
teamSize | string | — | Team-size band. Defaults to 11-25 when omitted. |
Parameters from the server's own tool schema.
This tool analyzes GTM stack configurations and returns calculated insights without modifying any systems, data, or configurations. It's a data retrieval and analysis function that provides recommendations rather than executing changes. The preview nature and reference to external audit links confirm it's informational only.
From the tool's definition Tool performs 'preview' analysis and 'get back' data (spend estimates, gaps, opportunities); returns information with 'link to full paid audit'. No modification verbs (create, update, delete, execute); read-only analysis of input parameters.
Attacks that exploit this kind of access
Run a preview StackScan: pass a list of tools + team size + industry, get back current spend, optimized spend, monthly/annual recoverable, headless gaps (tools with no MCP/API connection an owned head can call), and the top 5 replace/remove opportunities. Includes a link to the full paid audit on stackswap.ai. It is categorised as a Read tool in the StackSwap MCP Server, which means it retrieves data without modifying state.
scan_stack accepts 3 parameters: tools, industry, teamSize. 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 scan_stack: 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.
scan_stack 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 scan_stack 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 scan_stack. 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.
scan_stack 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.
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 →