run_quality_check · Crownpeak DQM MCP Server MCP

WHAT IT DOES

What run_quality_check does on Crownpeak DQM MCP Server

AI agents invoke run_quality_check to trigger actions in Crownpeak DQM 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 run_quality_check needs a policy

This tool triggers an external operation (quality scanning) that processes arguments (URL or HTML content) to produce side effects (asset creation and scanning results). While not destructive and not a direct financial operation, the ability to trigger arbitrary scans on URLs or content with potential asset creation makes this an Execute category risk.

From the tool's definition The tool 'run_quality_check' performs scanning operations on provided content ('scan it') and 'will create an asset', indicating it executes external quality checking logic against user-supplied inputs whose effects depend on the URL or content provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_quality_check Rate-limited

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": {
    "run_quality_check": {
      "limits": [
        {
          "counter": "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 Crownpeak DQM MCP Server, so you can run agents against it safely.

FAQ

Questions about run_quality_check

What does the run_quality_check tool do? +

Run a quality check on a URL or HTML content. This will create an asset, scan it, and return the results. It is categorised as a Execute tool in the Crownpeak DQM 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 run_quality_check? +

Register the Crownpeak DQM MCP Server MCP server in PolicyLayer and add a rule for 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 Crownpeak DQM MCP Server. Nothing to install.

What risk level is run_quality_check? +

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 run_quality_check? +

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

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

run_quality_check is provided by the Crownpeak DQM MCP Server MCP server (ptylr/crownpeak-dqm-node-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.