Archive an item in a GitHub Project
AI agents use archive-project-item to create or update resources in GitHub Projects MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub Projects MCP Server environment.
Archiving is a Write operation—it modifies project item state reversibly. Unlike deletion, archived items can typically be unarchived. The blast radius is medium because misuse could hide important project items from view, disrupting team workflows, but the action is not permanent or financially consequential.
From the tool's definition Tool name 'archive-project-item' and description 'Archive an item in a GitHub Project' indicate a reversible state change operation.
Documented attack patterns abuse exactly the kind of access archive-project-item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Projects MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for archive-project-item:
{
"version": "1",
"default": "deny",
"tools": {
"archive-project-item": {
"limits": [
{
"counter": "archive-project-item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}archive-project-item stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Archive an item in a GitHub Project. It is categorised as a Write tool in the GitHub Projects MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub Projects MCP Server MCP server in PolicyLayer and add a rule for archive-project-item: 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 MCP Server. Nothing to install.
archive-project-item 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 archive-project-item 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 archive-project-item. 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.
archive-project-item is provided by the GitHub Projects MCP Server MCP server (taylor-lindores-reeves/mcp-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 21 GitHub Projects MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 GitHub Projects MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.