Create a named checkpoint with an auto-captured screenshot. MCP Enabled.
AI agents use sitebay_create_checkpoint to create or update resources in SiteBay MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SiteBay MCP Server environment.
This tool creates and stores checkpoint data (named snapshots with screenshots) on the SiteBay platform, which is a write operation. While checkpoints are typically reversible and useful for recovery, the creation of state artifacts qualifies as Write rather than Read (which would only retrieve).
From the tool's definition The tool 'creates' a named checkpoint and 'auto-captures' a screenshot, indicating creation of data/state rather than retrieval or deletion. Checkpoints are reversible snapshots used for state management.
Attacks that exploit this kind of access
Create a named checkpoint with an auto-captured screenshot. MCP Enabled. It is categorised as a Write tool in the SiteBay MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_create_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 SiteBay MCP Server. Nothing to install.
sitebay_create_checkpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sitebay_create_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 sitebay_create_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.
sitebay_create_checkpoint is provided by the SiteBay MCP Server MCP server (sitebay/sitebay-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 →