agendas_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/agendas-update.md

WHAT IT DOES

What agendas_update does on Servicialo

AI agents use agendas_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
`slug`	string	—
`title`	string	—
`apiKey`	string	—
`orgSlug`	string	Yes
`agendaId`	string	Yes
`category`	string	—
`isActive`	boolean	—
`isPublic`	boolean	—
`expiresAt`	string	—
`isDefault`	boolean	—
`description`	string	—
`proveedorId`	string	—

Parameters from the server's own tool schema.

RISK

Why agendas_update is rated Medium

Modifies agenda settings reversibly affecting booking behavior and data visibility across professional service delivery platform.

From the tool's definition Update public agenda configuration, visibility, booking flow, selection modes, privacy flags, provider/service linking.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

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

agendas_update Rate-limited

agendas_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": {
    "agendas_update": {
      "limits": [
        {
          "counter": "agendas_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 agendas_update call is checked against it from then on.

FAQ

Questions about agendas_update

What does the agendas_update tool do? +

Update a public agenda’s configuration. Partial update — only provided fields are changed. Supports modifying: title, description, visibility (isPublic/isActive), booking flow order (service_first/provider_first/auto), selection modes for service and provider (required/optional/auto/hidden), assignment strategy (manual/round_robin/least_booked/most_available/priority/random), privacy flags (showSessions, showClientNames, showProviderUtilization, showProviderList), prepayment, and provider/service linking. When a provider is assigned, their services are auto-linked to the agenda. 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 agendas_update accept? +

agendas_update accepts 12 parameters: slug, title, apiKey, orgSlug, agendaId, category, isActive, isPublic, expiresAt, isDefault, description, proveedorId. Required: orgSlug, agendaId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on agendas_update? +

Register the Servicialo MCP server in PolicyLayer and add a rule for agendas_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 agendas_update? +

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

Can I rate-limit agendas_update? +

Yes. Add a rate_limit block to the agendas_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 agendas_update completely? +

Set action: deny in the PolicyLayer policy for agendas_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 agendas_update? +

agendas_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 →