provider_create
Create a new provider in the organization. Links or creates a Person record by email.
This record as markdown: /tools/com-servicialo-mcp-server/provider-create.md
What provider_create does on Servicialo
AI agents use provider_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 | |
email | string | Yes | |
phone | string | — | |
apiKey | string | — | |
orgSlug | string | Yes | |
lastName | string | Yes | |
isInternal | boolean | — | |
serviceIds | array | — | |
idempotencyKey | string | — | |
comunasCobertura | array | — | |
defaultCommission | number | — |
Parameters from the server's own tool schema.
Why provider_create is rated Medium
The tool creates new provider records and person entries, which are write operations that modify system state. While reversible (records can typically be deleted or modified later), the creation of organizational entities with potential downstream effects (e.g., access grants, contact lists) warrants medium severity.
From the tool's definition Tool name contains 'create' and description states 'Create a new provider in the organization. Links or creates a Person record by email.' This is a reversible creation operation that modifies organizational data.
Risk signalsHandles credentials or secrets (apiKey) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs provider_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 provider_create, this is the rule to start with:
provider_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 provider_create call is checked against it from then on.
Questions about provider_create
Create a new provider in the organization. Links or creates a Person record by email. 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.
provider_create accepts 11 parameters: name, email, phone, apiKey, orgSlug, lastName, isInternal, serviceIds, idempotencyKey, comunasCobertura, defaultCommission. Required: name, email, orgSlug, lastName. 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 provider_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.
provider_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 provider_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 provider_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.
provider_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