search_services
Search across Fixidu's full catalog (every bookable item across every category) by keyword, matching item title, category, and sub-category. Returns matching items with id, title, price, category, and a real image URL. Use this when the user asks about a specific kind of service, e.g. 'AC repair'...
This record as markdown: /tools/com-fixidu-mcp-server/search-services.md
What search_services does on Fixidu
AI agents call search_services to retrieve information from Fixidu 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 |
|---|---|---|---|
keyword | string | Yes | Search term, e.g. 'AC repair', 'switch replacement', 'deep cleaning' |
Parameters from the server's own tool schema.
Why search_services is rated Low
Even though search_services only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_services safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fixidu, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_services, this is the rule to start with:
search_services 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 Fixidu, apply this rule, and every search_services call is checked against it from then on.
Questions about search_services
Search across Fixidu's full catalog (every bookable item across every category) by keyword, matching item title, category, and sub-category. Returns matching items with id, title, price, category, and a real image URL. Use this when the user asks about a specific kind of service, e.g. 'AC repair' or 'switch replacement'. It is categorised as a Read tool in the Fixidu MCP Server, which means it retrieves data without modifying state.
search_services accepts 1 parameter: keyword. Required: keyword. The full parameter table on this page comes from the server's own tool schema.
Register the Fixidu MCP server in PolicyLayer and add a rule for search_services: 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 Fixidu. Nothing to install.
search_services 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_services 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_services. 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_services is provided by the Fixidu MCP server (https://mcp.fixidu.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fixidu, and thousands of servers like it.
This server
Across the catalogue