checks.update · Stillonline MCP: Risk & Policy

WHAT IT DOES

What checks.update does on Stillonline

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

WHY IT NEEDS A POLICY

Why checks.update needs a policy

This tool modifies existing monitoring check configuration (pausing/resuming monitoring, renaming, changing probe intervals). These changes are reversible — a paused check can be resumed, a renamed check can be renamed back — placing it firmly in the Write category. Misuse could cause monitoring gaps (e.g., pausing all checks), giving it medium severity.

From the tool's definition Update a StillOnline check. Use this to pause or resume monitoring, rename a check, or change its probe interval

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

checks.update Rate-limited

checks.update 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": {
    "checks.update": {
      "limits": [
        {
          "counter": "checks.update_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 Stillonline, so you can run agents against it safely.

FAQ

Questions about checks.update

What does the checks.update tool do? +

Update a StillOnline check. Use this to pause or resume monitoring, rename a check, or change its probe interval after deploy or infrastructure changes. It is categorised as a Write tool in the Stillonline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on checks.update? +

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

What risk level is checks.update? +

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

Can I rate-limit checks.update? +

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

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

checks.update is provided by the Stillonline MCP server (shenwell/stillonline-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.