create_property · Sanka MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_property does on Sanka MCP Server

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

This tool creates new properties in Sanka or connected CRM systems, which is a reversible data modification operation. It does not execute arbitrary code, delete data, or handle financial transactions. The 'medium' severity reflects that unauthorized property creation could affect data schema integrity and CRM configuration, but can typically be reversed through deletion or update operations.

From the tool's definition Tool name 'create_property' and description explicitly states it 'Create[s] a custom property' which modifies data by adding new properties to Sanka or connected CRM systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_property Rate-limited

create_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": {
    "create_property": {
      "limits": [
        {
          "counter": "create_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 create_property

What does the create_property tool do? +

Create a 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. Do not use this for company billing_cycle or payment_cycle; those are standard company fields set through create_company/update_company. 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 create_property? +

Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for create_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 create_property? +

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

Can I rate-limit create_property? +

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

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

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