Reset all system email templates to their factory defaults (overwrites customisations)
AI agents call reset_system_templates to permanently remove resources in Prowpt MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly destroys user customizations by overwriting them with defaults. While the data (email templates) may technically still exist, the custom modifications are permanently lost and cannot be undone.
From the tool's definition Tool description states it 'overwrites customisations' when resetting system email templates to factory defaults. This is irreversible data loss—custom configurations cannot be recovered once overwritten.
Attacks that exploit this kind of access
Reset all system email templates to their factory defaults (overwrites customisations). It is categorised as a Destructive tool in the Prowpt MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for reset_system_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 Prowpt MCP Server. Nothing to install.
reset_system_templates is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reset_system_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 reset_system_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.
reset_system_templates is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-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 →