# add_template

A write tool on the 1c Templates MCP server.

Agent View of the PolicyLayer registry record for `add_template`. HTML page: https://policylayer.com/tools/desko77-1c-templates-mcp/add-template

## Facts

- Tool: `add_template`
- Server: 1c Templates (`desko77/1c-templates-mcp`) — https://policylayer.com/tools/desko77-1c-templates-mcp.md
- Homepage: https://github.com/Desko77/1c-templates-mcp
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "add_template",
    "arguments": {}
  }
}
```

## Why add_template is rated Medium

The 'add_template' tool creates new templates in the 1C code template repository. This is a Write operation—it creates data reversibly without destructive effects. Severity is medium because: (1) templates are added to a community repository and could introduce malicious code if an agent is manipulated into creating harmful templates, and (2) it modifies shared infrastructure, though additions can be deleted/edited.

From the tool's own definition: "Tool name 'add_template' indicates creation of new data. Server description mentions 'CRUD web interface' confirming create/read/update/delete operations are supported."

## Use case

AI agents use add_template to create or update resources in 1c Templates, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 1c Templates environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 1c Templates:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_template": {
      "limits": [
        {
          "counter": "add_template_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 1c Templates (5)

- `delete_template` — Destructive — https://policylayer.com/tools/desko77-1c-templates-mcp/delete-template.md
- `get_template` — Read — https://policylayer.com/tools/desko77-1c-templates-mcp/get-template.md
- `list_templates` — Read — https://policylayer.com/tools/desko77-1c-templates-mcp/list-templates.md
- `templatesearch` — Read — https://policylayer.com/tools/desko77-1c-templates-mcp/templatesearch.md
- `update_template` — Write — https://policylayer.com/tools/desko77-1c-templates-mcp/update-template.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=desko77-1c-templates-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/desko77-1c-templates-mcp