get_master_schedule
Unified calendar view across all practices: bookings, sessions, and invoice due dates in chronological order. See all your commitments in one place.
This record as markdown: /tools/app-businys-mcp-server/get-master-schedule.md
What get_master_schedule does on Businys
AI agents call get_master_schedule to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_master_schedule is rated Low
This tool retrieves and displays calendar information (bookings, sessions, invoice due dates) in chronological order. It is purely informational with no capability to modify, execute, or delete data. The blast radius of misuse is minimal — an agent could at worst see scheduled commitments, which is a low-severity information disclosure. Classification as Read is appropriate.
From the tool's definition Tool description states it provides a 'Unified calendar view' and 'See all your commitments in one place' — these are read-only retrieval operations. No modification, deletion, or execution verbs are present.
Attacks that exploit this kind of access
The rule that runs get_master_schedule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_master_schedule, this is the rule to start with:
get_master_schedule is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every get_master_schedule call is checked against it from then on.
Questions about get_master_schedule
Unified calendar view across all practices: bookings, sessions, and invoice due dates in chronological order. See all your commitments in one place. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for get_master_schedule: 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 Businys. Nothing to install.
get_master_schedule is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_master_schedule 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 get_master_schedule. 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.
get_master_schedule is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue