List git-sync repositories linked to your account
AI agents call sitebay_get_git_sync_repos 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 merely retrieves information about existing git-sync repositories associated with the user's account. It does not create, modify, execute, delete, or trigger any operations—it only queries and returns data. This is a straightforward Read operation with minimal blast radius if misused by an AI agent, as it only exposes repository metadata.
From the tool's definition The tool name and description both indicate a listing/querying operation: 'List git-sync repositories'. The verb 'list' and the absence of any modification, execution, deletion, or side-effect language clearly position this as a retrieval action.
Attacks that exploit this kind of access
List git-sync repositories linked to your account. 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_git_sync_repos: 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_git_sync_repos 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_git_sync_repos 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_git_sync_repos. 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_git_sync_repos 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 →