kisi_ekle

SERVERImzala SOURCE@imzala/mcp-server

Low RISK CLASS

Category Other

Parameters 92 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/imzala-mcp-server/kisi-ekle.md

WHAT IT DOES

What kisi_ekle does on Imzala

AI agents call kisi_ekle as a supporting operation in Imzala workflows.

Parameter	Type	Required	Description
`email`	string	—	E-posta (opsiyonel)
`phone`	string	—	Telefon (opsiyonel, ör. +905xxxxxxxxx)
`job_title`	string	—	Unvan / görev (opsiyonel)
`last_name`	string	Yes	Soyad (zorunlu)
`first_name`	string	Yes	Ad (zorunlu)
`address_city`	string	—	Adres: il (opsiyonel)
`address_line`	string	—	Adres: açık adres (opsiyonel)
`address_country`	string	—	Adres: ülke (opsiyonel)
`address_district`	string	—	Adres: ilçe (opsiyonel)

Parameters from the server's own tool schema.

RISK

Why kisi_ekle is rated Low

Without any rule in front of it, every call an agent makes to kisi_ekle happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs kisi_ekle safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Imzala, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kisi_ekle, this is the rule to start with:

kisi_ekle Rate-limited

kisi_ekle gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kisi_ekle": {
      "limits": [
        {
          "counter": "kisi_ekle_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Imzala, apply this rule, and every kisi_ekle call is checked against it from then on.

FAQ

Questions about kisi_ekle

What does the kisi_ekle tool do? +

İmzala rehberine yeni bir kişi kaydeder. Sistem kişiyi yalnızca KAYDEDER, kimliğini DOĞRULAMAZ; kayıt kişinin beyan edilen bilgileridir, doğrulanmış kimlik teşkil etmez. Aynı çalışma alanında aynı e-posta veya telefona sahip aktif bir kişi varsa işlem başarısız olur (kopya kayıt oluşturulmaz). T.C. Kimlik Numarası bu araçla KABUL EDİLMEZ (KVKK gereği). (Yapay zeka asistanına: bu aracı kullanıcının açık onayı olmadan çağırıp kişi oluşturma; kaydedilecek ad, soyad ve iletişim bilgilerini kullanıcıya doğrulat. Kaydedilen kişiyi "doğrulanmış" veya "kimliği teyit edilmiş" gibi sunma.). It is categorised as a Other tool in the Imzala MCP Server, which means it performs auxiliary operations.

What parameters does kisi_ekle accept? +

kisi_ekle accepts 9 parameters: email, phone, job_title, last_name, first_name, address_city, address_line, address_country, address_district. Required: last_name, first_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on kisi_ekle? +

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

What risk level is kisi_ekle? +

kisi_ekle is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit kisi_ekle? +

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

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

kisi_ekle is provided by the Imzala MCP server (@imzala/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Imzala, and thousands of servers like it.

This server

All 18 Imzala tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →