check_page_spec · Qontinui MCP Server MCP: Risk & Policy

WHAT IT DOES

What check_page_spec does on Qontinui MCP Server

AI agents invoke check_page_spec to trigger actions in Qontinui 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 check_page_spec needs a policy

The tool executes active verification against a live UI environment, which constitutes running operations whose effects depend on the live state of the UI. This goes beyond passive reading — it loads pages and interacts with the live interface, making it an Execute-category action. Misuse could trigger unintended UI interactions across multiple displays.

From the tool's definition 'Run B-style spec verification against the live UI. Loads the page' — actively runs verification against a live UI, triggering external operations on real displays/workflows

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

check_page_spec Rate-limited

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

FAQ

Questions about check_page_spec

What does the check_page_spec tool do? +

Run B-style spec verification against the live UI. Loads the page. It is categorised as a Execute tool in the Qontinui 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 check_page_spec? +

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

What risk level is check_page_spec? +

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

Can I rate-limit check_page_spec? +

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

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

check_page_spec is provided by the Qontinui MCP Server MCP server (qontinui/qontinui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.