agendas_delete
Delete a public agenda permanently. Cascades to related sessions booked through this agenda, comments, and service configs. Requires confirm: true. Cannot be undone.
This record as markdown: /tools/com-servicialo-mcp-server/agendas-delete.md
What agendas_delete does on Servicialo
AI agents call agendas_delete to permanently remove resources in Servicialo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
confirm | boolean | Yes | |
orgSlug | string | Yes | |
agendaId | string | Yes |
Parameters from the server's own tool schema.
Why agendas_delete is rated Critical
This tool irreversibly deletes data (agendas, related sessions, comments, and service configs) with cascading effects across multiple related records. The description explicitly states 'permanently' and 'cannot be undone', meeting the Destructive category definition.
From the tool's definition Delete a public agenda permanently. Cascades to related sessions booked through this agenda, comments, and service configs. Cannot be undone.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs agendas_delete 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_delete, this is the rule to start with:
agendas_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every agendas_delete call is checked against it from then on.
Questions about agendas_delete
Delete a public agenda permanently. Cascades to related sessions booked through this agenda, comments, and service configs. Requires confirm: true. Cannot be undone. It is categorised as a Destructive tool in the Servicialo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
agendas_delete accepts 4 parameters: apiKey, confirm, orgSlug, agendaId. Required: confirm, orgSlug, agendaId. 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 agendas_delete: 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.
agendas_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the agendas_delete 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 agendas_delete. 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.
agendas_delete 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.
Across the catalogue