Capture the current state of selected DataModel subtrees into a checkpoint. Required: scope (array of instance paths). The plugin serializes those subtrees + their descendant scripts and returns a JSON payload that
AI agents call snapshot_checkpoint to retrieve information from Melo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and serializes DataModel state into a checkpoint for later comparison or review. It is a read-only operation that captures existing data without side effects. The snapshot is used for diffing and analysis (as mentioned in the server description's script diffing capability), not for executing code or modifying game state.
From the tool's definition "Capture the current state" and "serializes those subtrees" — the tool reads and snapshots game state without modifying it. No deletion, modification, execution, or financial impact.
Attacks that exploit this kind of access
Capture the current state of selected DataModel subtrees into a checkpoint. Required: scope (array of instance paths). The plugin serializes those subtrees + their descendant scripts and returns a JSON payload that. It is categorised as a Read tool in the Melo MCP Server, which means it retrieves data without modifying state.
Register the Melo MCP server in PolicyLayer and add a rule for snapshot_checkpoint: 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 Melo. Nothing to install.
snapshot_checkpoint 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 snapshot_checkpoint 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 snapshot_checkpoint. 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.
snapshot_checkpoint is provided by the Melo MCP server (yannyhl/linkedsword-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 →