service_create
Create a new bookable service in an existing organization. Use this for day-to-day service management (requires X-Org-Api-Key). For initial org setup, prefer admin_create_service instead. After creating, use service_assign_provider to link providers. A service without providers cannot accept book...
This record as markdown: /tools/com-servicialo-mcp-server/service-create.md
What service_create does on Servicialo
AI agents use service_create to create or update resources in Servicialo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicialo environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
price | number | Yes | |
apiKey | string | — | |
orgSlug | string | Yes | |
category | string | — | |
currency | string | — | |
duration | integer | Yes | |
modalidad | string | — | |
providerId | string | — | |
description | string | — | |
isDiscoverable | boolean | — | |
qualityCapture | object | — |
Parameters from the server's own tool schema.
Why service_create is rated Medium
This tool creates new service records within an organization, which is a reversible write operation. While it modifies organizational state and could enable downstream bookings if combined with other tools, the immediate action is data creation rather than execution of external effects or financial transactions.
From the tool's definition Tool description states "Create a new bookable service in an existing organization" - this creates new data records that are stored and can be used for future bookings.
Risk signalsHandles credentials or secrets (apiKey) · High parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs service_create 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_create, this is the rule to start with:
service_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create call is checked against it from then on.
Questions about service_create
Create a new bookable service in an existing organization. Use this for day-to-day service management (requires X-Org-Api-Key). For initial org setup, prefer admin_create_service instead. After creating, use service_assign_provider to link providers. A service without providers cannot accept bookings. Optional delivery-verification overrides per service: verificationLevel (none = silent auto-complete, legacy; default_confirm = both can confirm and silence auto-confirms after the org window; dual_confirm = the client must positively confirm, silence does NOT; documented = the provider must attach evidence) and qualityCapture (ask the client for a 1–5 rating on confirmation). Omit both to inherit the organization defaults. It is categorised as a Write tool in the Servicialo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
service_create accepts 12 parameters: name, price, apiKey, orgSlug, category, currency, duration, modalidad, providerId, description, isDiscoverable, qualityCapture. Required: name, price, orgSlug, duration. 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_create: 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_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the service_create 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_create. 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_create 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