get_schedule

What get_schedule does on Vultr MCP

AI agents call get_schedule to retrieve information from Vultr MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_schedule is rated Low

This tool retrieves schedule information with no indicated side effects. The naming convention and position among sibling read-only accessor tools (get_*, list_*) strongly suggests it queries rather than modifies or executes. Confidence is moderate (0.75) because the description is empty; however, the server context and tool name provide sufficient evidence for Read classification.

From the tool's definition Tool name 'get_schedule' and sibling context (get_gym, get_coach, get_event, list_gyms, list_coaches, list_events) indicate data retrieval. No description provided, but pattern matches other getter/list tools on BJJ gym data server.

The rule that runs get_schedule safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_schedule, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_schedule": {}
  }
}

Questions about get_schedule