Kula Ai

84 tools. 25 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated:

25 can modify or destroy data
59 read-only
84 tools total

Community server · catalogue entry verified 02/07/2026

How to control Kula Ai ↓

What Kula Ai exposes to your agents

Read (59) Write / Execute (22) Destructive / Financial (3)
Critical Risk

The most dangerous Kula Ai tools

25 of Kula Ai's 84 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Kula Ai

PolicyLayer is an MCP gateway — it sits between your AI agents and Kula Ai, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "cancel_interview": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "close_requisition": {
    "limits": [
      {
        "counter": "close_requisition_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "check_interviewers_availability": {
    "limits": [
      {
        "counter": "check_interviewers_availability_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Kula Ai — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON KULA AI →

Instant setup, no code required.

All 84 Kula Ai tools

WRITE 21 tools
Write close_requisition Close a requisition. Only requisitions in a closeable state can be closed. Write create_application_note Add a note to a specific application. Write create_candidate Create a new candidate in Kula. At least one of email or linkedin_url (in social_urls) is required. Write create_interview Schedule an interview against an application. Calendar invites and conference URL are provisioned asynchronous Write create_job_stage Create a new pipeline stage for a job. Write create_requisition Create a new requisition. When head_count exceeds 1, creates a group of linked requisitions. Use list_requisit Write create_user Invite a new user to the account. The user is created in the pending state and sent an invitation email. Requi Write create_webhook Create a new webhook subscription. Write disable_webhook Disable an active webhook. Write enable_webhook Enable a disabled webhook. Write mark_candidate_no_show Mark the candidate as a no-show on an in_progress or ended interview. Cannot be marked when a scorecard has be Write reactivate_user Reactivate a previously deactivated user. Write rotate_webhook_secret Rotate the signing secret for a webhook. Write undo_candidate_no_show Reverse a candidate no-show. Allowed only when meeting_status is candidate_no_show. Write update_application_note Update an existing note on an application. Write update_application_stage Update the stage of a specific application. Write update_candidate Update an existing candidate Write update_interview Update an existing interview. All fields are optional — only the supplied fields are modified. Write update_requisition Update an existing requisition. Cannot modify requisitions with closed, archived, or filled statuses. Pass all Write update_user Update an existing user. Only supplied fields are modified. Email and account status cannot be changed via thi Write update_webhook Update an existing webhook configuration. Only include fields you want to change.
READ 59 tools
Read check_interviewers_availability Compute free interview slots across the organizer + interviewers Read find_companies Search the global company catalog. Returned IDs map to Read find_currencies List currencies. Returned IDs map to Read find_degrees List academic degrees, optionally filtered by name. Useful for discovering valid degree options for candidate Read find_disciplines Search academic disciplines (fields of study). Read find_industries List industries used to classify companies. Paginated; useful for discovering valid industry options. Read find_institutions Search academic institutions. Returned IDs map to Read find_locations Search cities, states, and countries. The returned Read find_skills Search the global skill catalog. Returned IDs map to Read find_tags Search candidate tags (account-scoped). Returned IDs map to Read get_application Get details of a specific application. Only use when the user asks about a specific application. Read get_candidate Retrieve full details of a specific candidate by ID, including all applications, tags, skills, and location. Read get_email_template Get full details for a single email or calendar-invite template, including subject, body, and owner. Read get_interview Get full details for a single interview, including interviewers, candidate, conference URL, scorecard refs. Read get_interview_plan Read the interview plan configured on a job — stages with their pre-configured interview activities. Read get_interviewers_availability_result Poll for the result of a previous Read get_job Retrieve full details of a specific job by ID, including description and interview stages. Read get_job_post Get details of a specific job post from the job board. Only use when the user asks about a specific job board Read get_requisition Get detailed information about a specific requisition, including description and custom field values. Read get_role Retrieve a single role by ID. Response includes a Read get_scorecard_template Get full details for a single scorecard template — questions, feedback/rating descriptions, and segmentation. Read get_user Retrieve a single user by ID. Response includes a Read get_webhook Get details of a specific webhook. Read get_webhook_sample_payload Get a sample webhook payload for a specific event type. Read list_application_interviews List the interviews scheduled on a specific application. Same as Read list_application_notes List notes on a specific application. Read list_applications List job applications. Only use when the user explicitly asks about applications. Read list_candidates List candidates with simple filters: email, date ranges, and sorting. Read list_conference_hosts List users eligible to be the conference Read list_custom_fields List custom fields configured in the organization. The type parameter is required — specify job, candidate, re Read list_degrees List all available academic degrees. Read list_departments List all departments as a flat paginated list. Each record has a parent_id to reconstruct the hierarchy client Read list_email_templates List email and calendar-invite templates configured for the account. Per-interview snapshots and system templa Read list_industries List all available industries. Read list_interviews List interviews for the account. Supports rich multi-value filters: by job, application, candidate, interviewe Read list_job_posts List published job posts on the job board. Only use when the user explicitly asks about job board listings. Read list_job_stages List all pipeline stages for a specific job. Read list_jobs List jobs with SQL-based filters and sorting. Read list_milestones List all hiring milestones (pipeline stage groupings) in the organization. Read list_offices List all offices in the organization. Read list_rejection_reasons List all rejection reasons configured in the organization. Read list_requisition_fields List default and custom field definitions for requisitions. Hidden fields are excluded. Optionally filter by d Read list_requisitions List all requisitions for your account, respecting permissions. Read list_roles List roles available in the account. Use this to discover valid role_id values for create_user and update_user Read list_scorecard_submissions List scorecards for a specific application. Each scorecard may be linked to an interview, assessment, or revie Read list_scorecard_templates List scorecard templates configured for the account. Use this to discover Read list_sources List all candidate sources in the organization. Read list_stage_activities List all activities (actions) configured for a specific job stage. Read list_users List users in the organization. Defaults to active users; use the status filter to include pending, deactivate Read list_valid_organizers List users eligible to be the Read list_webhook_events List all available webhook event types you can subscribe to. Read list_webhook_logs List recent delivery logs for a webhook, including status and response details for each attempt. Read list_webhooks List all configured webhooks. Read search_candidates Search candidates using Elasticsearch with rich filters and cursor-based pagination. Read search_companies Search companies by name. Useful for autocompleting company names. Read search_disciplines Search academic disciplines by name. Useful for autocompleting field of study. Read search_institutions Search academic institutions by name. Useful for autocompleting university or school names. Read search_jobs Search jobs by title (partial match supported) with optional filters. Read search_locations Search locations by query. Useful for autocompleting city or region names.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Kula Ai

Can an AI agent delete data through the Kula Ai MCP server? +

Yes. The Kula Ai server exposes 3 destructive tools including cancel_interview, deactivate_user, delete_webhook. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Kula Ai? +

The Kula Ai server has 21 write tools including close_requisition, create_application_note, create_candidate. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Kula Ai.

How many tools does the Kula Ai MCP server expose? +

84 tools across 3 categories: Destructive, Read, Write. 59 are read-only. 25 can modify, create, or delete data.

How do I enforce a policy on Kula Ai? +

Register the Kula Ai MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Kula Ai tool call.

Deterministic rules across all 84 Kula Ai tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

84 Kula Ai tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.