Search retained Dolt history for a site and return matching change events with cache freshness metadata.
AI agents call sitebay_search_dolt_history 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 is a Read operation—it queries historical change events and returns them with metadata. However, the severity is elevated to medium rather than low because history/audit logs can contain sensitive information about site changes, configurations, or user actions that could be exploited by an agent to understand system vulnerabilities or past access patterns.
From the tool's definition The tool "search" for retained "history" and "return matching change events" indicates querying/retrieving historical data with no modification capabilities. The description explicitly states it returns data rather than modifying it.
Attacks that exploit this kind of access
Search retained Dolt history for a site and return matching change events with cache freshness metadata. 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_search_dolt_history: 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_search_dolt_history 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_search_dolt_history 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_search_dolt_history. 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_search_dolt_history 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 →