AI agents use update_interview to create or update resources in Kula Ai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kula Ai environment.
This tool modifies existing interview records, which is a reversible write operation. It does not delete, execute external commands, or move money. However, severity is high because interviews are critical recruiting workflow data—unauthorized modification could disrupt hiring processes, change candidate evaluations, or alter interview logistics (times, interviewers, notes), affecting multiple stakeholders.
From the tool's definition Tool name 'update_interview' and description 'Update an existing interview. All fields are optional — only the supplied fields are modified' indicate modification of existing data without deletion.
Attacks that exploit this kind of access
Update an existing interview. All fields are optional — only the supplied fields are modified. It is categorised as a Write tool in the Kula Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kula Ai MCP server in PolicyLayer and add a rule for update_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.
update_interview is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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 →