AI agents call get_interviewers_availability_result 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 polls for the result of a previously initiated check (likely from 'check_interviewers_availability'). Polling for results is a read operation—it retrieves data about the state of an asynchronous operation without creating, modifying, or deleting any data. The blast radius is minimal as it only fetches information about interviewer availability.
From the tool's definition Tool name 'get_interviewers_availability_result' and description 'Poll for the result of a previous' indicate a polling/retrieval operation. The verb 'get' and 'poll' are characteristic of read operations that retrieve status or results without modifying data.
Attacks that exploit this kind of access
Poll for the result of a previous. 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 get_interviewers_availability_result: 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.
get_interviewers_availability_result 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_interviewers_availability_result 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_interviewers_availability_result. 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_interviewers_availability_result 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 →