AI agents call check_interviewers_availability to retrieve information from Kula Ai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries availability information across organizer and interviewer calendars. It retrieves data to display free time slots, with no side effects. The absence of write, execute, or destructive operations places it firmly in the Read category. Severity is low because misuse would only expose scheduling information without enabling unauthorized actions on the recruiting system.
From the tool's definition Tool computes and retrieves free interview slots without modifying any data. The verb 'compute' and 'check' indicate a read-only query operation. No creation, modification, or deletion of scheduling data occurs.
Attacks that exploit this kind of access
Compute free interview slots across the organizer + interviewers. It is categorised as a Read tool in the Kula Ai MCP Server, which means it retrieves data without modifying state.
Register the Kula Ai MCP server in PolicyLayer and add a rule for check_interviewers_availability: 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.
check_interviewers_availability 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 check_interviewers_availability 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 check_interviewers_availability. 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.
check_interviewers_availability 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 →