smartling_remove_locale_from_project

Remove a locale from the project

Server Smartling MCP Server jacobolevy/smartling-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What smartling_remove_locale_from_project does on Smartling MCP Server

AI agents call smartling_remove_locale_from_project 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.

Why smartling_remove_locale_from_project needs a policy

Removing a locale from a project is a destructive action: it permanently deletes the locale's association with the project, which could result in loss of translation workflows, job assignments, and locale-specific settings. This is not easily reversible without re-adding and reconfiguring everything, and the blast radius is high given it could impact multilingual content delivery across an entire locale.

From the tool's definition 'Remove a locale from the project' — removing a locale is an irreversible operation that eliminates all locale-specific configuration and potentially associated translation data from the project.

Questions about smartling_remove_locale_from_project

What does the smartling_remove_locale_from_project tool do? +

Remove a locale from the project. 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.

How do I enforce a policy on smartling_remove_locale_from_project? +

Register the Smartling MCP Server MCP server in PolicyLayer and add a rule for smartling_remove_locale_from_project: 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.

What risk level is smartling_remove_locale_from_project? +

smartling_remove_locale_from_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit smartling_remove_locale_from_project? +

Yes. Add a rate_limit block to the smartling_remove_locale_from_project 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.

How do I block smartling_remove_locale_from_project completely? +

Set action: deny in the PolicyLayer policy for smartling_remove_locale_from_project. 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.

What MCP server provides smartling_remove_locale_from_project? +

smartling_remove_locale_from_project 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.