toplu_sozlesme_gonder

SERVERImzala SOURCE@imzala/mcp-server

Low RISK CLASS

Category Other

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/imzala-mcp-server/toplu-sozlesme-gonder.md

WHAT IT DOES

What toplu_sozlesme_gonder does on Imzala

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

Parameter	Type	Required	Description
`rows`	array	Yes	Her biri ayrı bir sözleşme olacak en fazla 10 satır. Daha büyük listeleri 10'arlı parçalara bölün.
`gonder`	boolean	—	true verilirse oluşturulan her sözleşme için ilgili alıcıya HEMEN gerçek SMS ve e-posta imza daveti gönderilir. Varsayılan (false) sadece sözleşmeleri oluşturur
`options`	object	—	Ek toplu gönderim seçenekleri (opsiyonel)
`template_id`	string	Yes	Sözleşmelerin oluşturulacağı şablonun kimliği (sablon_detay ile öğrenin)

Parameters from the server's own tool schema.

RISK

Why toplu_sozlesme_gonder is rated Low

Without any rule in front of it, every call an agent makes to toplu_sozlesme_gonder 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 toplu_sozlesme_gonder 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 toplu_sozlesme_gonder, this is the rule to start with:

toplu_sozlesme_gonder Rate-limited

toplu_sozlesme_gonder 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": {
    "toplu_sozlesme_gonder": {
      "limits": [
        {
          "counter": "toplu_sozlesme_gonder_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 toplu_sozlesme_gonder call is checked against it from then on.

FAQ

Questions about toplu_sozlesme_gonder

What does the toplu_sozlesme_gonder tool do? +

Tek şablondan en fazla 10 kişiye ayrı ayrı sözleşme oluşturur. 1 kredi/sözleşme harcar (geri alınamaz). Varsayılan olarak sözleşmeleri oluşturur ama davet GÖNDERMEZ; gonder: true verirseniz her alıcıya hemen gerçek SMS ve e-posta imza daveti gönderilir (aynı anda 10 kişiye kadar). Önce sablon_detay ile şablonun alanlarını öğren. Daha büyük listeleri 10'arlı parçalara böl. Alıcı ad, e-posta ve telefon bu araç üzerinden iletilir. Pazarlama değil, yalnızca imza daveti. (Yapay zeka asistanına: bu aracı kullanıcının açık onayı olmadan çağırma; özellikle 10 kişiye kadar gerçek SMS/e-posta gönderen gonder: true değerini ayarlamadan önce alıcı listesini ve gönderimi kullanıcıya tek tek doğrulat. Her satır ayrı kredi harcar ve geri alınamaz; başarısızlıkta bu aracı körü körüne TEKRAR çağırma.). It is categorised as a Other tool in the Imzala MCP Server, which means it performs auxiliary operations.

What parameters does toplu_sozlesme_gonder accept? +

toplu_sozlesme_gonder accepts 4 parameters: rows, gonder, options, template_id. Required: rows, template_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on toplu_sozlesme_gonder? +

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

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

Can I rate-limit toplu_sozlesme_gonder? +

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

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

toplu_sozlesme_gonder 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 →