consultar_reserva

Consulta el estado de una reserva existente en Aisha. Requiere el folio (por ejemplo FILOSALO-0003) Y el nombre con el que se hizo la reserva. Ambos deben coincidir: es la protección para que nadie consulte citas ajenas. Úsala cuando la persona pregunte "¿sigue en pie mi cita?" o quiera confirmar...

SERVERAisha SOURCEhttps://hi-aisha.com/mcp

Low RISK CLASS

Category Other

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-hi-aisha-aisha/consultar-reserva.md

WHAT IT DOES

What consultar_reserva does on Aisha

AI agents call consultar_reserva as a supporting operation in Aisha workflows.

Parameter	Type	Required	Description
`folio`	string	Yes
`nombre_cliente`	string	Yes

Parameters from the server's own tool schema.

RISK

Why consultar_reserva is rated Low

Without any rule in front of it, every call an agent makes to consultar_reserva happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

consultar_reserva Rate-limited

consultar_reserva gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "consultar_reserva": {
      "limits": [
        {
          "counter": "consultar_reserva_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about consultar_reserva

What does the consultar_reserva tool do? +

What parameters does consultar_reserva accept? +

consultar_reserva accepts 2 parameters: folio, nombre_cliente. Required: folio, nombre_cliente. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on consultar_reserva? +

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

What risk level is consultar_reserva? +

consultar_reserva is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit consultar_reserva? +

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

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

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

KEEP EXPLORING

More on Aisha, and thousands of servers like it.

This server

All 12 Aisha tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →