sync-tests | PolicyLayer

WHAT IT DOES

What sync-tests does on Frontend Test Generation & Code Review MCP Server

AI agents use sync-tests to create or update resources in Frontend Test Generation & Code Review MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Frontend Test Generation & Code Review MCP Server environment.

WHY IT NEEDS A POLICY

Why sync-tests needs a policy

The tool synchronizes code changes and outputs new or updated test code, which implies creating or modifying test files. This is a Write operation (reversible creation/modification of test code artifacts). It does not execute code, delete data, or involve financial transactions.

From the tool's definition "同步代码变更与测试用例，自动输出新增/更新的测试代码" — synchronizes code changes with test cases, automatically outputs new/updated test code

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync-tests Rate-limited

sync-tests stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync-tests": {
      "limits": [
        {
          "counter": "sync-tests_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Frontend Test Generation & Code Review MCP Server, so you can run agents against it safely.

FAQ

Questions about sync-tests

What does the sync-tests tool do? +

同步代码变更与测试用例，自动输出新增/更新的测试代码。\n\n. It is categorised as a Write tool in the Frontend Test Generation & Code Review MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sync-tests? +

Register the Frontend Test Generation & Code Review MCP Server MCP server in PolicyLayer and add a rule for sync-tests: 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 Frontend Test Generation & Code Review MCP Server. Nothing to install.

What risk level is sync-tests? +

sync-tests is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sync-tests? +

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

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

sync-tests is provided by the Frontend Test Generation & Code Review MCP Server MCP server (northseacoder/fe-testgen-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.