service_list
List services of an organization. Can filter by active status, discoverability, or category.
This record as markdown: /tools/com-servicialo-mcp-server/service-list.md
What service_list does on Servicialo
AI agents call 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 |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes | |
category | string | — | |
activeOnly | boolean | — | |
discoverableOnly | boolean | — |
Parameters from the server's own tool schema.
Why service_list is rated Low
This tool performs data retrieval only (list with optional filters), with no capability to create, modify, delete, or execute operations. The lowest blast radius would result from misuse—an AI agent could retrieve unwanted service information but cannot alter state or trigger external effects.
From the tool's definition Tool name 'service_list' and description 'List services of an organization' with filter parameters indicate a read-only query operation that retrieves and returns service data without modification or side effects.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs 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 service_list, this is the rule to start with:
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 service_list call is checked against it from then on.
Questions about service_list
List services of an organization. Can filter by active status, discoverability, or category. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
service_list accepts 5 parameters: apiKey, orgSlug, category, activeOnly, discoverableOnly. 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 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.
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 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 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.
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