Move a Yandex Tracker issue to a new status by executing a transition. Use get_transitions first to find available transition IDs. Some transitions require additional fields (e.g. resolution for
Part of the Yandex Tracker server.
Free to start. No card required.
AI agents use transition_issue to create or modify resources in Yandex Tracker. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call transition_issue repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Yandex Tracker.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"transition_issue": {
"limits": [
{
"counter": "transition_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Yandex Tracker policy for all 23 tools.
These attack patterns abuse exactly the kind of access transition_issue gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Move a Yandex Tracker issue to a new status by executing a transition. Use get_transitions first to find available transition IDs. Some transitions require additional fields (e.g. resolution for. It is categorised as a Write tool in the Yandex Tracker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Yandex Tracker MCP server in PolicyLayer and add a rule for transition_issue: 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 Yandex Tracker. Nothing to install.
transition_issue 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 transition_issue 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 transition_issue. 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.
transition_issue is provided by the Yandex Tracker MCP server (yandex-tracker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 Yandex Tracker tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.