init_templates
Initialize the bundled local template library. Skips templates that already exist by name.
This record as markdown: /tools/todos/init-templates.md
What init_templates does on Todos
AI agents use init_templates to create or update resources in Todos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
Why init_templates is rated Medium
This tool creates new template records in a local library. It is a write operation (initializing/creating templates) but is safe by design since it skips existing templates, making it non-destructive and idempotent. Blast radius is low as it only affects local template configuration.
From the tool's definition Initialize the bundled local template library. Skips templates that already exist by name.
Attacks that exploit this kind of access
The rule that runs init_templates safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For init_templates, this is the rule to start with:
init_templates 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 Todos, apply this rule, and every init_templates call is checked against it from then on.
Questions about init_templates
Initialize the bundled local template library. Skips templates that already exist by name. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for init_templates: 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 Todos. Nothing to install.
init_templates 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 init_templates 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 init_templates. 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.
init_templates is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
This server
Across the catalogue