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

sozlesme_audit

Bir sözleşmenin denetim izini (timeline) döndürür: sözleşme ne zaman oluşturuldu, hangi taraf ne zaman görüntüledi/imzaladı, ne zaman tamamlandı/iptal edildi. Aktör (ad/e-posta) ve IP bilgileri KVKK gereği maskelidir. Yalnızca kendi hesabınızdaki (veya organizasyon çalışma alanınızdaki) sözleşmel...

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

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

What sozlesme_audit does on Imzala

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

ParameterTypeRequiredDescription
demand_id string Yes Denetim izi (timeline) istenen sözleşmenin kimliği

Parameters from the server's own tool schema.

Why sozlesme_audit is rated Low

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

Questions about sozlesme_audit

What does the sozlesme_audit tool do? +

Bir sözleşmenin denetim izini (timeline) döndürür: sözleşme ne zaman oluşturuldu, hangi taraf ne zaman görüntüledi/imzaladı, ne zaman tamamlandı/iptal edildi. Aktör (ad/e-posta) ve IP bilgileri KVKK gereği maskelidir. Yalnızca kendi hesabınızdaki (veya organizasyon çalışma alanınızdaki) sözleşmelerde çalışır; sahiplik doğrulanır. Girdi: demand_id (sözleşme kimliği, sozlesme_durumu veya sozlesmelerim ile öğrenilir). It is categorised as a Other tool in the Imzala MCP Server, which means it performs auxiliary operations.

What parameters does sozlesme_audit accept? +

sozlesme_audit accepts 1 parameter: 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 sozlesme_audit? +

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

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

Can I rate-limit sozlesme_audit? +

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

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

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