update_property · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_property does on Sanka MCP Server

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

WHY IT NEEDS A POLICY

Why update_property needs a policy

This tool modifies existing properties in Sanka or connected CRM systems. It is a Write operation because it creates or modifies data reversibly (property updates can typically be reverted or modified again). The severity is medium because property updates could affect business logic, integrations, or workflows, but are not destructive (data is not deleted), not financial (no money moves), and not code execution.

From the tool's definition Tool name is 'update_property' and description states 'Update an existing custom property' — classic write operation that modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_property Rate-limited

update_property 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_property": {
      "limits": [
        {
          "counter": "update_property_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 Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about update_property

What does the update_property tool do? +

Update an existing custom property in Sanka or a connected CRM. When provider is supplied, the MCP never performs a Sanka-only mutation; omit provider for Sanka properties. It is categorised as a Write tool in the Sanka MCP Server 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_property? +

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

What risk level is update_property? +

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

Can I rate-limit update_property? +

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

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

update_property is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.