generate_dx_tests · Squirex Dev MCP: Risk & Policy

WHAT IT DOES

What generate_dx_tests does on Squirex Dev

AI agents use generate_dx_tests to create or update resources in Squirex Dev — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Squirex Dev environment.

WHY IT NEEDS A POLICY

Why generate_dx_tests needs a policy

This tool generates new test specifications (YAML files) as output, which is a data creation activity. While it doesn't execute code or delete data, it writes/generates artifacts that will be stored or used downstream.

From the tool's definition Tool converts scan violations into test specifications in YAML format and generates structured data artifacts. The description indicates it creates or produces new test definition files/outputs ('generate', 'Convert...into').

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_dx_tests Rate-limited

generate_dx_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": {
    "generate_dx_tests": {
      "limits": [
        {
          "counter": "generate_dx_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 Squirex Dev, so you can run agents against it safely.

FAQ

Questions about generate_dx_tests

What does the generate_dx_tests tool do? +

Convert Agentforce scan violations into Agentforce DX test specifications (YAML format) compatible with. It is categorised as a Write tool in the Squirex Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_dx_tests? +

Register the Squirex Dev MCP server in PolicyLayer and add a rule for generate_dx_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 Squirex Dev. Nothing to install.

What risk level is generate_dx_tests? +

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

Can I rate-limit generate_dx_tests? +

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

Set action: deny in the PolicyLayer policy for generate_dx_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 generate_dx_tests? +

generate_dx_tests is provided by the Squirex Dev MCP server (squirex-dev/squirex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

generate_dx_tests is one line of Squirex Dev's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →