AI agents use link_commit to create or update resources in Tickr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tickr environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
sha | string | Yes | Commit SHA hash |
url | string | — | Commit URL |
repo | string | — | Repository name |
author | string | — | Author name |
branch | string | — | Branch name |
number | string | Yes | Ticket display number, e.g. 'TKR-BUG-0042' |
message | string | — | Commit message |
Parameters from the server's own tool schema.
The tool creates a new association or metadata record rather than reading data (not Read). It is reversible (can be unlinked), not a permanent deletion (not Destructive). It does not execute code or shell commands (not Execute). It involves no financial transactions (not Financial).
From the tool's definition Tool name 'link_commit' and description 'Link a git commit to a ticket' indicate creating or establishing a relationship between a commit and a ticket. This creates or modifies metadata (the link/association) in the ticketing system.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Link a git commit to a ticket. It is categorised as a Write tool in the Tickr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
link_commit accepts 7 parameters: sha, url, repo, author, branch, number, message. Required: sha, number. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr MCP server in PolicyLayer and add a rule for link_commit: 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 Tickr. Nothing to install.
link_commit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the link_commit 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 link_commit. 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.
link_commit is provided by the Tickr MCP server (@k-system/tickr-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 →