Get the result of a specific point-in-time restore by ID
AI agents call sitebay_get_pit_restore 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 retrieves information about an existing point-in-time restore operation—it queries data without creating, modifying, deleting, or executing new actions. The 'Get' verb combined with 'by ID' clearly indicates a read-only lookup. No side effects or data changes occur from calling this tool.
From the tool's definition Tool name 'sitebay_get_pit_restore' and description 'Get the result of a specific point-in-time restore by ID' indicate a retrieval/query operation that fetches status or results of a previously initiated restore operation.
Attacks that exploit this kind of access
Get the result of a specific point-in-time restore by ID. 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_get_pit_restore: 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_get_pit_restore 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_get_pit_restore 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_get_pit_restore. 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_get_pit_restore 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 →