update_application_note · Kula Ai MCP: Risk & Policy

WHAT IT DOES

What update_application_note does on Kula Ai

AI agents use update_application_note 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 update_application_note needs a policy

This tool creates or modifies data reversibly within the Kula recruiting API. An AI agent could misuse it to alter application notes maliciously, affecting hiring decisions or candidate records, but the change is reversible via another update. The blast radius is limited to a single application's notes rather than system-wide, warranting medium severity rather than high.

From the tool's definition The tool 'update_application_note' modifies existing data ('Update an existing note') in a recruiting system, making it a write operation. It does not delete data (which would be Destructive), execute code (Execute), or move money (Financial).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_application_note Rate-limited

update_application_note 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": {
    "update_application_note": {
      "limits": [
        {
          "counter": "update_application_note_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 update_application_note

What does the update_application_note tool do? +

Update an existing note on an application. 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 update_application_note? +

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

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

Can I rate-limit update_application_note? +

Yes. Add a rate_limit block to the update_application_note 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 update_application_note completely? +

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

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