List all available project templates. Use this to discover template UIDs before calling tms_create_project_from_template. For interaction/conversational use, prefer tms_create_project_from_template_shorthand which matches templates by name and skips this lookup. (GET /api2/v1/projectTemplates)
AI agents call tms_list_project_templates to retrieve information from Phrase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries project template data without creating, modifying, deleting, or executing any operations. It is purely informational—a listing operation that enables discovery of existing resources. The GET HTTP method and read-only nature confirm Read category classification. Severity is low as exposure would only allow an agent to view available templates, with no ability to alter system state.
From the tool's definition Tool description states 'List all available project templates' and uses GET request method. The purpose is to 'discover template UIDs' with no modification or side effects.
Attacks that exploit this kind of access
List all available project templates. Use this to discover template UIDs before calling tms_create_project_from_template. For interaction/conversational use, prefer tms_create_project_from_template_shorthand which matches templates by name and skips this lookup. (GET /api2/v1/projectTemplates). It is categorised as a Read tool in the Phrase MCP Server, which means it retrieves data without modifying state.
Register the Phrase MCP server in PolicyLayer and add a rule for tms_list_project_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 Phrase. Nothing to install.
tms_list_project_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tms_list_project_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 tms_list_project_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.
tms_list_project_templates is provided by the Phrase MCP server (phrase-mcp-server). 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 →