Book an appointment with a local service business. Creates a booking record and adds the appointment to the business calendar. Returns a confirmation with reference number. ONLY call this if the business has 'booking' in its enabledFeatures array.
Part of the Qasper server.
Free to start. No card required.
AI agents call book_appointment to retrieve information from Qasper without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though book_appointment only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"book_appointment": {}
}
}See the full Qasper policy for all 7 tools.
These attack patterns abuse exactly the kind of access book_appointment gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Book an appointment with a local service business. Creates a booking record and adds the appointment to the business calendar. Returns a confirmation with reference number. ONLY call this if the business has 'booking' in its enabledFeatures array.. It is categorised as a Read tool in the Qasper MCP Server, which means it retrieves data without modifying state.
Register the Qasper MCP server in PolicyLayer and add a rule for book_appointment: 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 Qasper. Nothing to install.
book_appointment 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 book_appointment 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 book_appointment. 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.
book_appointment is provided by the Qasper MCP server (qasper/business-agents). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Qasper tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.