template-manage · MCP LLM Generator v2 MCP: Risk & Policy

WHAT IT DOES

What template-manage does on MCP LLM Generator v2

AI agents use template-manage to create or update resources in MCP LLM Generator v2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP LLM Generator v2 environment.

WHY IT NEEDS A POLICY

Why template-manage needs a policy

The tool creates (Add), modifies (Update), and removes (Delete) template records with file-based persistence. While it includes a delete operation, this is categorized as Write rather than Destructive because: (1) templates are typically user-created, non-critical data; (2) file-based persistence suggests recovery options; (3) the operation is reversible in practice.

From the tool's definition Tool description explicitly states 'Add, update, delete, and list templates' — the delete operation is reversible via file-based persistence (can restore from backups or re-upload), distinguishing it from destructive permanent deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

template-manage Rate-limited

template-manage 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "template-manage": {
      "limits": [
        {
          "counter": "template-manage_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP LLM Generator v2, so you can run agents against it safely.

FAQ

Questions about template-manage

What does the template-manage tool do? +

Add, update, delete, and list templates with file-based persistence. It is categorised as a Write tool in the MCP LLM Generator v2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on template-manage? +

Register the MCP LLM Generator v2 MCP server in PolicyLayer and add a rule for template-manage: 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 MCP LLM Generator v2. Nothing to install.

What risk level is template-manage? +

template-manage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit template-manage? +

Yes. Add a rate_limit block to the template-manage 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.

How do I block template-manage completely? +

Set action: deny in the PolicyLayer policy for template-manage. 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.

What MCP server provides template-manage? +

template-manage is provided by the MCP LLM Generator v2 MCP server (mako10k/mcp-llm-generator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.