update-template
AI agents use update-template to create or update resources in RunPod MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RunPod MCP Server environment.
The 'update-template' tool modifies template configurations within RunPod, which is reversible (unlike delete operations). This qualifies as Write category. Severity is high because templates control container deployments and infrastructure configurations—misconfigured updates could disrupt services or expose sensitive data in template definitions.
From the tool's definition Tool name 'update-template' indicates modification of a template resource. The server's sibling tools include create-template and delete-template, establishing a pattern where 'update' operations are reversible modifications to RunPod resources.
Attacks that exploit this kind of access
update-template. It is categorised as a Write tool in the RunPod MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RunPod MCP Server 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 RunPod MCP Server. 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 RunPod MCP Server MCP server (niel-runpod/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →