cancelar_cita_mia
Para el DUEÑO: cancelar una cita de su propio negocio. Se puede por folio, o por nombre del cliente y fecha. Si hay más de una coincidencia NO cancela ninguna: devuelve la lista para que el dueño diga cuál. Cancelar es irreversible desde aquí, así que nunca se adivina. Al confirmar, recuérdale al...
This record as markdown: /tools/com-hi-aisha-aisha/cancelar-cita-mia.md
What cancelar_cita_mia does on Aisha
AI agents call cancelar_cita_mia to permanently remove resources in Aisha, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
clave | string | Yes | |
fecha | string | — | |
folio | string | — | |
negocio | string | Yes | |
nombre_cliente | string | — |
Parameters from the server's own tool schema.
Why cancelar_cita_mia is rated Critical
An AI agent that decides to call cancelar_cita_mia doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Aisha is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs cancelar_cita_mia safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aisha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancelar_cita_mia, this is the rule to start with:
cancelar_cita_mia 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 Aisha, apply this rule, and every cancelar_cita_mia call is checked against it from then on.
Questions about cancelar_cita_mia
Para el DUEÑO: cancelar una cita de su propio negocio. Se puede por folio, o por nombre del cliente y fecha. Si hay más de una coincidencia NO cancela ninguna: devuelve la lista para que el dueño diga cuál. Cancelar es irreversible desde aquí, así que nunca se adivina. Al confirmar, recuérdale al dueño que le avise al cliente — Aisha no le escribe a la persona por él. It is categorised as a Destructive tool in the Aisha MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cancelar_cita_mia accepts 5 parameters: clave, fecha, folio, negocio, nombre_cliente. Required: clave, negocio. The full parameter table on this page comes from the server's own tool schema.
Register the Aisha MCP server in PolicyLayer and add a rule for cancelar_cita_mia: 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 Aisha. Nothing to install.
cancelar_cita_mia 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 cancelar_cita_mia 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 cancelar_cita_mia. 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.
cancelar_cita_mia is provided by the Aisha MCP server (https://hi-aisha.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aisha, and thousands of servers like it.
Across the catalogue