Update task status and optionally add a comment in a GitHub Project (V2)
Part of the GitHub Projects server.
Free to start. No card required.
AI agents use manage_task_status to create or modify resources in GitHub Projects. 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 manage_task_status 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 GitHub Projects.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"manage_task_status": {
"limits": [
{
"counter": "manage_task_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full GitHub Projects policy for all 19 tools.
These attack patterns abuse exactly the kind of access manage_task_status 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.
Update task status and optionally add a comment in a GitHub Project (V2). It is categorised as a Write tool in the GitHub Projects MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub Projects MCP server in PolicyLayer and add a rule for manage_task_status: 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 Projects. Nothing to install.
manage_task_status 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 manage_task_status 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 manage_task_status. 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.
manage_task_status is provided by the GitHub Projects MCP server (devassistantai/github-projects). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 GitHub Projects 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.