Get a comprehensive overview of a CodeUp repository including basic info, branches, recent commits, and merge requests in one read-only call. This is the best starting point when exploring a new repository.
AI agents call get_repository_overview to retrieve information from Yunxiao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mrLimit | number | — | Max merge requests returned. Defaults to 5. |
mrState | string | — | Merge request state filter: opened, merged, or closed. Defaults to opened. |
refName | string | — | Branch, tag, or commit SHA for commit listing. Defaults to the repository default branch when omitted. |
branchLimit | number | — | Max branches returned. Defaults to 5. |
commitLimit | number | — | Max commits returned. Defaults to 5. |
repositoryId | string | Yes | Repository ID (numeric ID or full path like org/repo). Use list_repositories to find the repository ID. |
includeCommits | boolean | — | Whether to include recent commits. Defaults to true. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
includeBranches | boolean | — | Whether to include branch list. Defaults to true. |
includeMergeRequests | boolean | — | Whether to include merge requests. Defaults to true. |
Parameters from the server's own tool schema.
This tool retrieves repository metadata and history without modifying, executing, or deleting anything. The explicit 'read-only' designation confirms it belongs in the Read category. Severity is low because repository overview data is typically non-sensitive metadata that misuse would not significantly harm the DevOps platform.
From the tool's definition Tool description explicitly states 'read-only call' and lists retrieval operations: 'basic info, branches, recent commits, and merge requests.' The verb 'Get' and framing as 'best starting point when exploring' indicate data retrieval with no side effects.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
Get a comprehensive overview of a CodeUp repository including basic info, branches, recent commits, and merge requests in one read-only call. This is the best starting point when exploring a new repository. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
get_repository_overview accepts 10 parameters: mrLimit, mrState, refName, branchLimit, commitLimit, repositoryId, includeCommits, organizationId, includeBranches, includeMergeRequests. Required: repositoryId. The full parameter table on this page comes from the server's own tool schema.
Register the Yunxiao MCP server in PolicyLayer and add a rule for get_repository_overview: 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 Yunxiao. Nothing to install.
get_repository_overview 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 get_repository_overview 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 get_repository_overview. 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.
get_repository_overview is provided by the Yunxiao MCP server (@futuretea/yunxiao-mcp-server). 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 →