Get recent Dolt commits for a site
AI agents call sitebay_dolt_log to retrieve information from SiteBay MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that returns metadata about recent commits. There is no data modification, deletion, execution of commands, or financial impact. The blast radius of misuse is minimal—an agent could only retrieve version control history, which is typically non-sensitive operational data. This is a straightforward Read classification.
From the tool's definition The tool name 'sitebay_dolt_log' and description 'Get recent Dolt commits for a site' indicate a retrieval operation that queries commit history from a Dolt version control system. It retrieves historical data with no modification or side effects.
Attacks that exploit this kind of access
Get recent Dolt commits for a site. It is categorised as a Read tool in the SiteBay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SiteBay MCP Server MCP server in PolicyLayer and add a rule for sitebay_dolt_log: 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_dolt_log 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 sitebay_dolt_log 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_dolt_log. 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_dolt_log 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 →