List all checkpoints (quality rules), optionally filtered by website
AI agents call list_checkpoints to retrieve information from Crownpeak DQM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates checkpoint data (quality rules) from the DQM system, potentially filtered by website. It performs no mutations, deletions, executions, or financial operations. The 'list' verb and passive retrieval nature classify it as a Read operation. Severity is low because listing configuration data poses minimal risk; the worst case is information disclosure about existing quality rules.
From the tool's definition Tool name 'list_checkpoints' and description 'List all checkpoints (quality rules), optionally filtered by website' indicate a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
List all checkpoints (quality rules), optionally filtered by website. It is categorised as a Read tool in the Crownpeak DQM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Crownpeak DQM MCP Server MCP server in PolicyLayer and add a rule for list_checkpoints: 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.
list_checkpoints 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 list_checkpoints 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 list_checkpoints. 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.
list_checkpoints 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.
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 →