# list_templates

A read tool on the 1c Templates MCP server.

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

## Facts

- Tool: `list_templates`
- 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: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why list_templates is rated Low

The tool retrieves or lists template data without modification. Even though the description is empty, the name strongly indicates a list/retrieval operation typical of Read category tools. No side effects or data mutation occurs. Severity is low because listing templates poses minimal risk—it retrieves information that exists, with limited blast radius if misused by an agent.

From the tool's own definition: "Tool name 'list_templates' with no description provided; based on naming convention and context (CRUD interface for templates), this is a retrieval/enumeration operation. Sibling tools include write/delete operations, positioning this as a read-only sibling."

## Use case

AI agents call list_templates to retrieve information from 1c Templates without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_templates": {}
  }
}
```

## 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
- `templatesearch` — Read — https://policylayer.com/tools/desko77-1c-templates-mcp/templatesearch.md
- `add_template` — Write — https://policylayer.com/tools/desko77-1c-templates-mcp/add-template.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