Low Risk

checkup_scan

Scan a Next.js project for production-readiness gaps. Returns findings with severity levels and vendor-neutral recommendations.

How to control checkup_scan ↓

What checkup_scan does on Clocktower

AI agents call checkup_scan to retrieve information from Clocktower without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why checkup_scan needs a policy

This tool retrieves and queries information about a Next.js project's configuration and readiness status, returning analytical results. It has no side effects, does not execute code, and does not modify data. It is purely a diagnostic/read operation that fits the 'Read' category for data retrieval with no side effects.

From the tool's definition Tool name 'checkup_scan' and description indicate it performs scanning and analysis ('Scan a Next.js project for production-readiness gaps. Returns findings').

Documented attack patterns abuse exactly the kind of access checkup_scan gives an agent:

How to control checkup_scan

PolicyLayer is an MCP gateway — it sits between your AI agents and Clocktower, and nothing reaches the server without passing your rules. This is the rule we recommend for checkup_scan:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "checkup_scan": {}
  }
}

checkup_scan is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Clocktower — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about checkup_scan

What does the checkup_scan tool do? +

Scan a Next.js project for production-readiness gaps. Returns findings with severity levels and vendor-neutral recommendations. It is categorised as a Read tool in the Clocktower MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on checkup_scan? +

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

What risk level is checkup_scan? +

checkup_scan is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit checkup_scan? +

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

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

checkup_scan is provided by the Clocktower MCP server (sathergate/sathergate-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Clocktower tool call.

Start from Clocktower, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

26 Clocktower tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.