import_templates
Import templates from JSON data. Returns summary with imported count, skipped duplicates, and errors.
This record as markdown: /tools/instantkom-mcp-server/import-templates.md
What import_templates does on instantKOM MCP Server
AI agents use import_templates to create or update resources in instantKOM MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your instantKOM MCP Server environment.
Why import_templates is rated Medium
This tool creates or adds template records to the instantKOM platform, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). The moderate severity reflects that bulk template imports could affect system configuration and messaging capabilities, but the operation is reversible by deleting imported templates.
From the tool's definition Tool description states 'Import templates from JSON data' which creates new template records in the system. The return of 'imported count, skipped duplicates, and errors' indicates data creation/insertion operations.
Attacks that exploit this kind of access
The rule that runs import_templates safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_templates, this is the rule to start with:
import_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 instantKOM MCP Server, apply this rule, and every import_templates call is checked against it from then on.
Questions about import_templates
Import templates from JSON data. Returns summary with imported count, skipped duplicates, and errors. It is categorised as a Write tool in the instantKOM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for import_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 instantKOM MCP Server. Nothing to install.
import_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 import_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 import_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.
import_templates is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
This server
Across the catalogue