mark_candidate_no_show · Kula Ai MCP: Risk & Policy

WHAT IT DOES

What mark_candidate_no_show does on Kula Ai

AI agents use mark_candidate_no_show 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.

WHY IT NEEDS A POLICY

Why mark_candidate_no_show needs a policy

This is a Write operation because it modifies existing data (candidate interview record) in a reversible manner—marking a candidate as no-show can presumably be undone or corrected. It does not delete data (Destructive), execute arbitrary code (Execute), nor move money (Financial).

From the tool's definition Tool 'mark_candidate_no_show' updates candidate interview status by marking them as no-show. Description explicitly states it modifies interview state ('Mark the candidate as a no-show') with conditions ('Cannot be marked when a scorecard has been…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_candidate_no_show Rate-limited

mark_candidate_no_show stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mark_candidate_no_show": {
      "limits": [
        {
          "counter": "mark_candidate_no_show_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kula Ai, so you can run agents against it safely.

FAQ

Questions about mark_candidate_no_show

What does the mark_candidate_no_show tool do? +

Mark the candidate as a no-show on an in_progress or ended interview. Cannot be marked when a scorecard has been submitted. 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.

How do I enforce a policy on mark_candidate_no_show? +

Register the Kula Ai MCP server in PolicyLayer and add a rule for mark_candidate_no_show: 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.

What risk level is mark_candidate_no_show? +

mark_candidate_no_show is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mark_candidate_no_show? +

Yes. Add a rate_limit block to the mark_candidate_no_show 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.

How do I block mark_candidate_no_show completely? +

Set action: deny in the PolicyLayer policy for mark_candidate_no_show. 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.

What MCP server provides mark_candidate_no_show? +

mark_candidate_no_show 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.