List HTTP and SSL checks for a StillOnline project. Use this before updating, pausing, deleting, or auditing monitor coverage.
AI agents call checks.list to retrieve information from Stillonline without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries monitoring check data for a StillOnline project without creating, modifying, or deleting any resources. It has no side effects and poses minimal risk if invoked by an AI agent, as it only returns informational data about existing checks.
From the tool's definition Tool name is 'checks.list' and description states 'List HTTP and SSL checks' — a retrieval operation with no modification of state.
Attacks that exploit this kind of access
List HTTP and SSL checks for a StillOnline project. Use this before updating, pausing, deleting, or auditing monitor coverage. It is categorised as a Read tool in the Stillonline MCP Server, which means it retrieves data without modifying state.
Register the Stillonline MCP server in PolicyLayer and add a rule for checks.list: 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.
checks.list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the checks.list 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.
Set action: deny in the PolicyLayer policy for checks.list. 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.
checks.list 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →