search_tools
Search the available FavCRM tool catalog for relevant operations. Use this when the curated direct tool list does not contain the operation you need.
This record as markdown: /tools/io-favcrm-favcrm/search-tools.md
What search_tools does on FavCRM
AI agents call search_tools to retrieve information from FavCRM without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum results (default 8, max 20) |
query | string | — | Plain-language tool search, e.g. "delete a segment" or "set custom field values" |
scope | string | — | Optional exact scope filter, e.g. contacts, customer_segments, invoices |
write | boolean | — | Filter to write tools (true) or read-only tools (false) |
includeInputSchema | boolean | — | Include full JSON input schemas for returned tools. Defaults to false to keep context small. |
Parameters from the server's own tool schema.
Why search_tools is rated Low
This is a metadata search/discovery function. It retrieves information about the tool catalog to help users find relevant operations. No side effects, no code execution, no data modification or deletion. The tool itself is passive and informational, making it a Read operation with low severity.
From the tool's definition Tool name and description indicate 'Search the available FavCRM tool catalog' — a query operation that retrieves information about available tools without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs search_tools safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_tools, this is the rule to start with:
search_tools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every search_tools call is checked against it from then on.
Questions about search_tools
Search the available FavCRM tool catalog for relevant operations. Use this when the curated direct tool list does not contain the operation you need. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
search_tools accepts 5 parameters: limit, query, scope, write, includeInputSchema. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for search_tools: 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 FavCRM. Nothing to install.
search_tools 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_tools 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_tools. 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_tools is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue