smartling_run_quality_check · Smartling MCP Server MCP

WHAT IT DOES

What smartling_run_quality_check does on Smartling MCP Server

AI agents invoke smartling_run_quality_check to trigger actions in Smartling MCP Server. 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.

WHY IT NEEDS A POLICY

Why smartling_run_quality_check needs a policy

This tool triggers execution of quality check operations on translation data. While quality checks are typically non-destructive read operations, the 'run' verb and the automation of quality processes indicates active execution of a workflow step rather than simple data retrieval.

From the tool's definition Tool name contains 'run' and description states 'Run quality checks on translation content', indicating execution of an automated process on specified translation content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

smartling_run_quality_check Rate-limited

smartling_run_quality_check stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "smartling_run_quality_check": {
      "limits": [
        {
          "counter": "smartling_run_quality_check_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Smartling MCP Server, so you can run agents against it safely.

FAQ

Questions about smartling_run_quality_check

What does the smartling_run_quality_check tool do? +

Run quality checks on translation content. It is categorised as a Execute tool in the Smartling MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on smartling_run_quality_check? +

Register the Smartling MCP Server MCP server in PolicyLayer and add a rule for smartling_run_quality_check: 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_run_quality_check? +

smartling_run_quality_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit smartling_run_quality_check? +

Yes. Add a rate_limit block to the smartling_run_quality_check 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_run_quality_check completely? +

Set action: deny in the PolicyLayer policy for smartling_run_quality_check. 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_run_quality_check? +

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