New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

search_vendors

Search any theme's data index by free-text query across vendor name, domain, integrations, plan notes, and capabilities (e.g. 'hipaa restaurant', 'google ads zapier'). Works for every theme — hub sections and catalog topics alike (set section to the theme slug from list_sections). Returns full pr...

SERVERThe Front Desk Review SOURCEhttps://mcp.frontdeskreview.com/mcp
Low RISK CLASS
Category Read
Parameters 20 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-frontdeskreview-front-desk-review-data/search-vendors.md

What search_vendors does on The Front Desk Review

AI agents call search_vendors to retrieve information from The Front Desk Review without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
query string
section string Theme slug to query (default "ai-receptionists"). A theme is any of the 271 pricing topics this index covers: the deep hub sections (e.g. ai-receptionists) plus

Parameters from the server's own tool schema.

Why search_vendors is rated Low

This is a read-only search/query operation across a vendor database. It retrieves and returns information based on free-text search criteria but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal — an agent could only over-query or retrieve broad datasets, with no ability to alter or harm underlying data.

From the tool's definition Tool performs 'Search' and 'Returns full provenanced vendor records' — retrieves data without modification. No language indicating side effects, state changes, or destructive operations.

Risk signalsBulk/mass operation — affects multiple targets

Questions about search_vendors

What does the search_vendors tool do? +

Search any theme's data index by free-text query across vendor name, domain, integrations, plan notes, and capabilities (e.g. 'hipaa restaurant', 'google ads zapier'). Works for every theme — hub sections and catalog topics alike (set section to the theme slug from list_sections). Returns full provenanced vendor records (each plan carries source url + accessedAt). Empty query returns all vendors in the theme. It is categorised as a Read tool in the The Front Desk Review MCP Server, which means it retrieves data without modifying state.

What parameters does search_vendors accept? +

search_vendors accepts 2 parameters: query, section. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on search_vendors? +

Register the The Front Desk Review MCP server in PolicyLayer and add a rule for search_vendors: 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 The Front Desk Review. Nothing to install.

What risk level is search_vendors? +

search_vendors is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_vendors? +

Yes. Add a rate_limit block to the search_vendors 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.

How do I block search_vendors completely? +

Set action: deny in the PolicyLayer policy for search_vendors. 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.

What MCP server provides search_vendors? +

search_vendors is provided by the The Front Desk Review MCP server (https://mcp.frontdeskreview.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on The Front Desk Review, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of The Front Desk Review's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.