Full-text search across StackSwap's first-party GTM knowledge base — ~50 operator-narrative articles on stack architecture, AI-native swaps, RevOps, data ethics, and decision frameworks. Returns ranked articles with title, slug, category, summary, and URL. Use when the user asks a GTM strategy/ar...
AI agents call search_content 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 |
|---|---|---|---|
limit | integer | — | Max number of results. |
query | string | Yes | Free-text search query. Multi-word queries are scored on per-term hits. |
category | string | — | Optional category filter (slug or label). Known slugs: gtm-infrastructure, stack-design, ai-automation, data-ethics. |
Parameters from the server's own tool schema.
This tool retrieves and queries data with no side effects. It matches the 'Read' category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The tool explicitly returns informational articles for reference purposes. No data is created, modified, deleted, or executed; it is purely a search and retrieval mechanism over static knowledge base content.
From the tool's definition Tool description states it is a 'Full-text search' across 'StackSwap's first-party GTM knowledge base' that 'Returns ranked articles with title, slug, category, summary, and URL.' The server description emphasizes these are '8 read-only tools' and the tool…
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Full-text search across StackSwap's first-party GTM knowledge base — ~50 operator-narrative articles on stack architecture, AI-native swaps, RevOps, data ethics, and decision frameworks. Returns ranked articles with title, slug, category, summary, and URL. Use when the user asks a GTM strategy/architecture/methodology question that's been written about (e.g. 'how should I think about CRM migration', 'what's wrong with intent data', 'how to audit my stack'). Cite the URL in your reply. Pass slug to get_kb_article for the full body. It is categorised as a Read tool in the StackSwap MCP Server, which means it retrieves data without modifying state.
search_content accepts 3 parameters: limit, query, category. Required: query. 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 search_content: 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.
search_content 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 search_content 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 search_content. 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.
search_content 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 →