update_template
A write tool on the 1c Templates MCP server.
This record as markdown: /tools/desko77-1c-templates-mcp/update-template.md
What update_template does on 1c Templates
AI agents use update_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.
Why update_template is rated Medium
The name and context strongly suggest reversible modification of template data within the 1C code template collection. This is a Write operation—data is created or modified but can be reversed (e.g., overwritten or restored). Without destructive operations like permanent deletion or financial impact, and absent evidence of arbitrary code execution, this falls below Execute and Destructive severity.
From the tool's definition Tool name 'update_template' combined with server's stated 'CRUD web interface' and sibling operations (add_template, delete_template, get_template) indicates data modification capability. The empty description prevents confirmation of exact scope.
Attacks that exploit this kind of access
The rule that runs update_template safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1c Templates, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_template, this is the rule to start with:
update_template stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 1c Templates, apply this rule, and every update_template call is checked against it from then on.
Questions about update_template
update_template is a write tool on the 1c Templates MCP server. It is categorised as a Write tool in the 1c Templates MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 1c Templates MCP server in PolicyLayer and add a rule for update_template: 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 1c Templates. Nothing to install.
update_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_template 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 update_template. 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.
update_template is provided by the 1c Templates MCP server (desko77/1c-templates-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1c Templates, and thousands of servers like it.
This server
Across the catalogue