push_to_testing_center · Squirex Dev MCP: Risk & Policy

WHAT IT DOES

What push_to_testing_center does on Squirex Dev

AI agents invoke push_to_testing_center to trigger actions in Squirex Dev. 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 push_to_testing_center needs a policy

This tool pushes a test specification to an external Salesforce service (Testing Center), triggering an external operation whose effects depend on the arguments provided. It is not merely writing local data — it delegates execution to an external system. This warrants Execute classification.

From the tool's definition 'Push an Agentforce DX test spec to the Salesforce Testing Center. Delegates to' — the tool pushes/triggers an external operation against Salesforce Testing Center

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

push_to_testing_center Rate-limited

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

FAQ

Questions about push_to_testing_center

What does the push_to_testing_center tool do? +

Push an Agentforce DX test spec to the Salesforce Testing Center. Delegates to. It is categorised as a Execute tool in the Squirex Dev MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on push_to_testing_center? +

Register the Squirex Dev MCP server in PolicyLayer and add a rule for push_to_testing_center: 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 push_to_testing_center? +

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

Can I rate-limit push_to_testing_center? +

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

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

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