Get repository status including last commit and branch info.
AI agents call getRepositoryStatus to retrieve information from GitHub 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 repository information (last commit, branch details) without performing any side effects. It is a query/fetch operation that has no capacity to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only gather information about repository state.
From the tool's definition Tool name 'getRepositoryStatus' and description 'Get repository status including last commit and branch info' indicate retrieval of metadata with no modification or execution capability.
Attacks that exploit this kind of access
Get repository status including last commit and branch info. It is categorised as a Read tool in the GitHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for getRepositoryStatus: 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 GitHub MCP Server. Nothing to install.
getRepositoryStatus 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 getRepositoryStatus 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 getRepositoryStatus. 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.
getRepositoryStatus is provided by the GitHub MCP Server MCP server (j-nowcow/github-mcp-practice). 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 →