kanka_update_entity · Kanka MCP: Risk & Policy

WHAT IT DOES

What kanka_update_entity does on Kanka

AI agents use kanka_update_entity to create or update resources in Kanka — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kanka environment.

WHY IT NEEDS A POLICY

Why kanka_update_entity needs a policy

This tool creates or modifies data in a reversible manner (PATCH operation), fitting the Write category. It is not Destructive because PATCH updates are reversible and do not permanently erase data. Severity is medium because unintended modifications to campaign entities could disrupt data integrity, but the impact is limited to updates rather than deletions, and changes can be corrected.

From the tool's definition Tool performs 'Partial update (PATCH) on an existing entity' which modifies data reversibly. The description explicitly states it updates existing entities with provided fields.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kanka_update_entity Rate-limited

kanka_update_entity 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": {
    "kanka_update_entity": {
      "limits": [
        {
          "counter": "kanka_update_entity_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 Kanka, so you can run agents against it safely.

FAQ

Questions about kanka_update_entity

What does the kanka_update_entity tool do? +

Partial update (PATCH) on an existing entity. Provide only the fields you want to change. The. It is categorised as a Write tool in the Kanka MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on kanka_update_entity? +

Register the Kanka MCP server in PolicyLayer and add a rule for kanka_update_entity: 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 Kanka. Nothing to install.

What risk level is kanka_update_entity? +

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

Can I rate-limit kanka_update_entity? +

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

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

kanka_update_entity is provided by the Kanka MCP server (torinvdb/kanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.