service_update

SERVERServicialo SOURCE@servicialo/mcp-server

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/service-update.md

WHAT IT DOES

What service_update does on Servicialo

AI agents use service_update 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
`name`	string	—
`price`	number	—
`apiKey`	string	—
`orgSlug`	string	Yes
`category`	string	—
`currency`	string	—
`duration`	integer	—
`isActive`	boolean	—
`modalidad`	string	—
`serviceId`	string	Yes
`description`	string	—
`isDiscoverable`	boolean	—

Parameters from the server's own tool schema.

RISK

Why service_update is rated Medium

This tool modifies service records reversibly through update operations. While it touches price-related data, it does not execute payment transactions or financial transfers; it updates service metadata and pricing configuration. The Write category applies as the primary action is modification of existing data structures.

From the tool's definition Tool description states 'Update an existing service (price, duration, status, etc.)' and 'Creates a price history entry if price changes.' This explicitly modifies service data including financially-relevant attributes (price) and operational parameters…

Risk signalsHandles credentials or secrets (apiKey) · High parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs service_update 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_update, this is the rule to start with:

service_update Rate-limited

service_update 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "service_update": {
      "limits": [
        {
          "counter": "service_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every service_update call is checked against it from then on.

FAQ

Questions about service_update

What does the service_update tool do? +

Update an existing service (price, duration, status, etc.). Creates a price history entry if price changes. Delivery-verification overrides can be changed too: verificationLevel (none / default_confirm / dual_confirm / documented — see service_create for semantics) and qualityCapture (1–5 rating on confirmation). Pass null on either to reset that field and inherit the organization default again; omit to leave it unchanged. 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.

What parameters does service_update accept? +

service_update accepts 12 parameters: name, price, apiKey, orgSlug, category, currency, duration, isActive, modalidad, serviceId, description, isDiscoverable. Required: orgSlug, serviceId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on service_update? +

Register the Servicialo MCP server in PolicyLayer and add a rule for service_update: 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.

What risk level is service_update? +

service_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit service_update? +

Yes. Add a rate_limit block to the service_update 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.

How do I block service_update completely? +

Set action: deny in the PolicyLayer policy for service_update. 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.

What MCP server provides service_update? +

service_update 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.

KEEP EXPLORING

More on Servicialo, and thousands of servers like it.

This server

All 111 Servicialo tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →