mi_agenda

Para el DUEÑO de un negocio: ver cómo va su día en Aisha. Requiere la clave de su panel (la del enlace de su agenda). Devuelve las citas de ese día con quién viene, qué servicio y a qué hora, más las horas que quedan libres. Sin fecha, muestra hoy.

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

Low RISK CLASS

Category Other

Parameters 32 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/mi-agenda.md

WHAT IT DOES

What mi_agenda does on Aisha

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

Parameter	Type	Required
`clave`	string	Yes
`fecha`	string	—
`negocio`	string	Yes

Parameters from the server's own tool schema.

RISK

Why mi_agenda is rated Low

Without any rule in front of it, every call an agent makes to mi_agenda 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 mi_agenda 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 mi_agenda, this is the rule to start with:

mi_agenda Rate-limited

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

FAQ

Questions about mi_agenda

What does the mi_agenda tool do? +

What parameters does mi_agenda accept? +

mi_agenda accepts 3 parameters: clave, fecha, negocio. Required: clave, negocio. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on mi_agenda? +

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

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

Can I rate-limit mi_agenda? +

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

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

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