AI agents call list_commits 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 |
|---|---|---|---|
page | number | — | Page number for pagination. Starts at 1. |
path | string | — | Filter commits touching this path. |
since | string | — | Start time in ISO 8601 format. |
until | string | — | End time in ISO 8601 format. |
search | string | — | Commit search keyword. |
perPage | number | — | Page size for pagination. Supports 1-100. Defaults to 100 when omitted. |
refName | string | Yes | Branch, tag, or commit SHA. |
committerIds | string | — | Comma-separated committer user IDs. |
repositoryId | string | Yes | Repository numeric ID or full path such as org/repo. |
showSignature | boolean | — | Whether to include commit signatures. |
organizationId | string | — | Yunxiao organization ID. When omitted, the server uses the user's default organization. |
Parameters from the server's own tool schema.
This tool retrieves and queries commit history from a version control system. It performs a read-only operation that displays existing data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could only access commit metadata that is typically already visible to repository members.
From the tool's definition Tool name 'list_commits' and description 'List commits in a CodeUp repository. Use this to review recent changes and commit history' indicate retrieval of commit history data with no modification or side effects.
Risk signalsAccepts file system path (path) · High parameter count (11 properties)
Attacks that exploit this kind of access
List commits in a CodeUp repository. Use this to review recent changes and commit history. It is categorised as a Read tool in the Yunxiao MCP Server, which means it retrieves data without modifying state.
list_commits accepts 11 parameters: page, path, since, until, search, perPage, refName, committerIds, repositoryId, showSignature, organizationId. Required: refName, 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 list_commits: 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.
list_commits 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 list_commits 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 list_commits. 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.
list_commits 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 →