Cancel a scheduled interview. Calendar events are torn down and cancellation notifications dispatched asynchronously.
AI agents call cancel_interview to permanently remove resources in Kula Ai — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling an interview tears down calendar events and sends cancellation notifications — these actions are irreversible (the interview slot is lost, notifications already sent) and have significant downstream effects on candidates and interviewers, making this Destructive with high severity.
From the tool's definition 'Cancel a scheduled interview. Calendar events are torn down and cancellation notifications dispatched asynchronously.'
Attacks that exploit this kind of access
Cancel a scheduled interview. Calendar events are torn down and cancellation notifications dispatched asynchronously. It is categorised as a Destructive tool in the Kula Ai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kula Ai MCP server in PolicyLayer and add a rule for cancel_interview: 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 Kula Ai. Nothing to install.
cancel_interview is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_interview 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 cancel_interview. 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.
cancel_interview is provided by the Kula Ai MCP server (kula-ai/kula-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →