raporlar
İmzala hesabınızın (veya organizasyon çalışma alanınızın) sözleşme özetini döndürür: toplam sözleşme sayısı, duruma göre dağılım (bekleyen / tamamlanan / iptal / süresi dolmuş) ve bu ay oluşturulan sözleşme sayısı. Yalnızca sayı döner, taraf bilgisi (PII) içermez. "Kaç sözleşmem tamamlandı?", "bu...
This record as markdown: /tools/imzala-mcp-server/raporlar.md
What raporlar does on Imzala
AI agents call raporlar as a supporting operation in Imzala workflows.
Why raporlar is rated Low
Without any rule in front of it, every call an agent makes to raporlar happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Attacks that exploit this kind of access
The rule that runs raporlar 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 raporlar, this is the rule to start with:
raporlar gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Imzala, apply this rule, and every raporlar call is checked against it from then on.
Questions about raporlar
İmzala hesabınızın (veya organizasyon çalışma alanınızın) sözleşme özetini döndürür: toplam sözleşme sayısı, duruma göre dağılım (bekleyen / tamamlanan / iptal / süresi dolmuş) ve bu ay oluşturulan sözleşme sayısı. Yalnızca sayı döner, taraf bilgisi (PII) içermez. "Kaç sözleşmem tamamlandı?", "bu ay kaç sözleşme oluşturdum?" gibi soruları cevaplar. It is categorised as a Other tool in the Imzala MCP Server, which means it performs auxiliary operations.
Register the Imzala MCP server in PolicyLayer and add a rule for raporlar: 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.
raporlar is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the raporlar 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.
Set action: deny in the PolicyLayer policy for raporlar. 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.
raporlar 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.
This server
Across the catalogue