browse_service
Given a service category id (from list_service_categories), return what's inside it: either bookable catalog items with prices and images directly, or its sub-categories (drill in again with the sub-category's catalog) — mirrors how the Fixidu app itself branches.
This record as markdown: /tools/com-fixidu-mcp-server/browse-service.md
What browse_service does on Fixidu
AI agents call browse_service 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 |
|---|---|---|---|
serviceId | string | number | Yes | A service category id from list_service_categories |
Parameters from the server's own tool schema.
Why browse_service is rated Low
Even though browse_service 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 browse_service 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 browse_service, this is the rule to start with:
browse_service 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 browse_service call is checked against it from then on.
Questions about browse_service
Given a service category id (from list_service_categories), return what's inside it: either bookable catalog items with prices and images directly, or its sub-categories (drill in again with the sub-category's catalog) — mirrors how the Fixidu app itself branches. It is categorised as a Read tool in the Fixidu MCP Server, which means it retrieves data without modifying state.
browse_service accepts 1 parameter: serviceId. Required: serviceId. 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 browse_service: 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.
browse_service 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 browse_service 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 browse_service. 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.
browse_service 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