Semantic search over super-kit agents, skills, workflows, and SUPERKIT.md. Returns the most relevant heading-level chunks. Use BEFORE load_superkit_skill/agent/workflow to find what you need without loading full files.
AI agents call search_context to retrieve information from Superkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
topK | number | — | Number of results to return (1-20) |
query | string | Yes | Natural language search query |
Parameters from the server's own tool schema.
This tool retrieves and queries data (search over agents, skills, workflows, and documentation) with no side effects. It does not create, modify, delete, or execute any operations. It is purely informational and enables discovery of existing resources, making it a Read operation with low severity due to minimal blast radius if misused.
From the tool's definition The tool performs 'semantic search' and 'returns the most relevant heading-level chunks.' It queries existing documentation and resources without modifying, deleting, or executing any operations.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Semantic search over super-kit agents, skills, workflows, and SUPERKIT.md. Returns the most relevant heading-level chunks. Use BEFORE load_superkit_skill/agent/workflow to find what you need without loading full files. It is categorised as a Read tool in the Superkit MCP Server, which means it retrieves data without modifying state.
search_context accepts 2 parameters: topK, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Superkit MCP server in PolicyLayer and add a rule for search_context: 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 Superkit. Nothing to install.
search_context 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_context 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_context. 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_context is provided by the Superkit MCP server (superkit-mcp-server). 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 →