sablon_detay
Bir şablonun detayını gösterir: taraflar ve doldurulabilir değişkenler. Şablondan sözleşme oluşturmadan önce hangi değişkenlerin gerektiğini öğrenmek için kullanılır.
This record as markdown: /tools/imzala-mcp-server/sablon-detay.md
What sablon_detay does on Imzala
AI agents call sablon_detay as a supporting operation in Imzala workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
template_id | string | Yes | Detayı istenen şablonun kimliği |
Parameters from the server's own tool schema.
Why sablon_detay is rated Low
Without any rule in front of it, every call an agent makes to sablon_detay 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 sablon_detay 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 sablon_detay, this is the rule to start with:
sablon_detay 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 sablon_detay call is checked against it from then on.
Questions about sablon_detay
Bir şablonun detayını gösterir: taraflar ve doldurulabilir değişkenler. Şablondan sözleşme oluşturmadan önce hangi değişkenlerin gerektiğini öğrenmek için kullanılır. It is categorised as a Other tool in the Imzala MCP Server, which means it performs auxiliary operations.
sablon_detay accepts 1 parameter: template_id. Required: template_id. The full parameter table on this page comes from the server's own tool schema.
Register the Imzala MCP server in PolicyLayer and add a rule for sablon_detay: 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.
sablon_detay 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 sablon_detay 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 sablon_detay. 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.
sablon_detay 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