Match keywords from the user's request against domain file hooks — precise machine-level intent detection without AI inference. Call this with keywords from the user's request, then call cairn_domain() for each matched domain to load relevant design context.
Part of the Cairn MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke cairn_match to trigger processes or run actions in Cairn. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
cairn_match can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
cairn_match:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Cairn policy for all 6 tools.
Agents calling execute-class tools like cairn_match have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
cairn_match is one of the high-risk operations in Cairn. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Match keywords from the user's request against domain file hooks — precise machine-level intent detection without AI inference. Call this with keywords from the user's request, then call cairn_domain() for each matched domain to load relevant design context.. It is categorised as a Execute tool in the Cairn MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for cairn_match. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cairn MCP server.
cairn_match is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cairn_match rule in your Intercept 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 Intercept policy for cairn_match. 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.
cairn_match is provided by the Cairn MCP server (cairn-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.