run_template
AI agents invoke run_template to trigger actions in Claude Team MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool name 'run_template' most naturally maps to Execute rather than Write because it performs runtime instantiation and execution of templated code/commands rather than merely storing or modifying template definitions. While the empty description limits confidence, the term 'run' is a strong indicator of execution semantics.
From the tool's definition Tool name 'run_template' indicates execution of a template, likely with variable substitution or code generation. In the context of a multi-agent coding team MCP server, templates typically contain code, scripts, or commands that are instantiated and executed.
Attacks that exploit this kind of access
run_template. It is categorised as a Execute tool in the Claude Team MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Team MCP server in PolicyLayer and add a rule for run_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 Claude Team MCP. Nothing to install.
run_template is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_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 run_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.
run_template is provided by the Claude Team MCP server (lakshan12367/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 →