New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

hatirlatma_gonder

Bir sözleşmede henüz imzalamamış taraflara gerçek SMS ve e-posta hatırlatması gönderir. Bu araç gerçek mesaj gönderir (iletişim işlemi). Aynı sözleşmeye 5 dakika içinde tekrar hatırlatma engellenir (zorla: true ile aşılabilir); kişi başına en fazla 3 SMS ve 3 e-posta gönderilir. (Yapay zeka asist...

SERVERImzala SOURCE@imzala/mcp-server
Low RISK CLASS
Category Other
Parameters 31 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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

What hatirlatma_gonder does on Imzala

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

ParameterTypeRequiredDescription
zorla boolean true verilirse 5 dakikalık bekleme süresi aşılır (kişi başı 3 SMS + 3 e-posta sınırı yine geçerli)
kanallar array Hangi kanallardan gönderilsin (varsayılan: ikisi de)
demand_id string Yes Hatırlatma gönderilecek sözleşmenin kimliği

Parameters from the server's own tool schema.

Why hatirlatma_gonder is rated Low

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

Questions about hatirlatma_gonder

What does the hatirlatma_gonder tool do? +

Bir sözleşmede henüz imzalamamış taraflara gerçek SMS ve e-posta hatırlatması gönderir. Bu araç gerçek mesaj gönderir (iletişim işlemi). Aynı sözleşmeye 5 dakika içinde tekrar hatırlatma engellenir (zorla: true ile aşılabilir); kişi başına en fazla 3 SMS ve 3 e-posta gönderilir. (Yapay zeka asistanına: bu araç kullanıcının onayı olmadan gerçek mesaj göndermek için kullanılmamalı.). It is categorised as a Other tool in the Imzala MCP Server, which means it performs auxiliary operations.

What parameters does hatirlatma_gonder accept? +

hatirlatma_gonder accepts 3 parameters: zorla, kanallar, demand_id. Required: demand_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hatirlatma_gonder? +

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

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

Can I rate-limit hatirlatma_gonder? +

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

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

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

More on Imzala, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Imzala's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.