public_service_list
List publicly bookable services for an organization. Does NOT require an API key. Returns only active, discoverable services with assigned providers. Use this as the first step in the public booking flow to show available services to end users or agents.
This record as markdown: /tools/com-servicialo-mcp-server/public-service-list.md
What public_service_list does on Servicialo
AI agents call public_service_list to retrieve information from Servicialo 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 |
|---|---|---|---|
orgSlug | string | Yes |
Parameters from the server's own tool schema.
Why public_service_list is rated Low
This tool performs a simple read/query operation on publicly available service data. It requires no authentication, returns only active and discoverable information, and explicitly does not modify any state. The blast radius of misuse is minimal — an agent could at worst retrieve a list of services it shouldn't see, but no data is created, modified, deleted, or executed. This is a straightforward Read category tool.
From the tool's definition Tool description states it 'List publicly bookable services' and 'Returns only active, discoverable services' — purely a data retrieval operation with no side effects or modifications.
Attacks that exploit this kind of access
The rule that runs public_service_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Servicialo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For public_service_list, this is the rule to start with:
public_service_list 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 Servicialo, apply this rule, and every public_service_list call is checked against it from then on.
Questions about public_service_list
List publicly bookable services for an organization. Does NOT require an API key. Returns only active, discoverable services with assigned providers. Use this as the first step in the public booking flow to show available services to end users or agents. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
public_service_list accepts 1 parameter: orgSlug. Required: orgSlug. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for public_service_list: 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 Servicialo. Nothing to install.
public_service_list 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 public_service_list 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 public_service_list. 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.
public_service_list is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Servicialo, and thousands of servers like it.
This server
Across the catalogue