sync_templates · MCP Prompt Template Selector MCP

WHAT IT DOES

What sync_templates does on MCP Prompt Template Selector

AI agents use sync_templates to create or update resources in MCP Prompt Template Selector — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Prompt Template Selector environment.

WHY IT NEEDS A POLICY

Why sync_templates needs a policy

The tool performs a synchronization operation that retrieves templates from an external source (GitHub) and updates internal state (local index). This constitutes a Write operation—reversible data modification. It's not Destructive because it doesn't irreversibly delete or overwrite existing data; syncing typically merges or updates.

From the tool's definition The tool description states it 'Sync templates from the GitHub repository and update the local index,' which involves fetching external data and modifying local state (updating the index). This is a data modification operation, not a deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_templates Rate-limited

sync_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_templates": {
      "limits": [
        {
          "counter": "sync_templates_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 Prompt Template Selector, so you can run agents against it safely.

FAQ

Questions about sync_templates

What does the sync_templates tool do? +

Sync templates from the GitHub repository and update the local index. It is categorised as a Write tool in the MCP Prompt Template Selector MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sync_templates? +

Register the MCP Prompt Template Selector MCP server in PolicyLayer and add a rule for sync_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 MCP Prompt Template Selector. Nothing to install.

What risk level is sync_templates? +

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

Can I rate-limit sync_templates? +

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

How do I block sync_templates completely? +

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

What MCP server provides sync_templates? +

sync_templates is provided by the MCP Prompt Template Selector MCP server (vadimber2/mcp-prompt-tool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.