AI agents call list_checkpoints to retrieve information from Maestro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
List operations typically retrieve and display data without side effects. The name pattern and sibling tools (which include destructive operations like 'atualizar_codebase' and 'auto_fix') suggest this is a simple introspection tool. Low severity because listing checkpoints poses minimal risk even if misused. Confidence reduced to 0.7 due to sparse description, but the semantics of 'list_' are clear enough.
From the tool's definition Tool name 'list_checkpoints' indicates a listing/retrieval operation with no modification capability. Description is minimal and uninformative ('[Interno] Use'), but the 'list' prefix strongly suggests read-only enumeration.
Attacks that exploit this kind of access
[Interno] Use. It is categorised as a Read tool in the Maestro MCP Server, which means it retrieves data without modifying state.
Register the Maestro 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 Maestro. 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 Maestro MCP server (matheus-gama-deluna/maestro). 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 →