Delete a file from Smartling
AI agents call smartling_delete_file to permanently remove resources in Smartling MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (files) from Smartling. Deletion cannot be undone without external backup restoration. While not a financial impact, the destruction of translation assets, project files, or associated content represents a high-severity risk if invoked erroneously by an AI agent, potentially disrupting multilingual workflows and losing work.
From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete a file from Smartling' — a permanent removal operation.
Attacks that exploit this kind of access
Delete a file from Smartling. It is categorised as a Destructive tool in the Smartling MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Smartling MCP Server MCP server in PolicyLayer and add a rule for smartling_delete_file: 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 Smartling MCP Server. Nothing to install.
smartling_delete_file 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 smartling_delete_file 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 smartling_delete_file. 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.
smartling_delete_file is provided by the Smartling MCP Server MCP server (jacobolevy/smartling-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 →