Mark a GitHub Project as a template
AI agents use mark-project-as-template 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.
This is a Write operation because it creates or modifies data reversibly. Marking a project as a template changes project settings but does not delete data or create destructive side effects. The action is reversible—a template designation can be removed. Severity is medium because misuse could affect project visibility and sharing behavior for team members, but it doesn't destroy data or have financial impact.
From the tool's definition The tool marks a project as a template, which modifies project metadata/properties. The description explicitly states it will mark/change the project's template status, a configuration modification that is reversible (can be unmarked later).
Documented attack patterns abuse exactly the kind of access mark-project-as-template 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 mark-project-as-template:
{
"version": "1",
"default": "deny",
"tools": {
"mark-project-as-template": {
"limits": [
{
"counter": "mark-project-as-template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mark-project-as-template 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.
Mark a GitHub Project as a template. 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 mark-project-as-template: 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.
mark-project-as-template 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 mark-project-as-template 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 mark-project-as-template. 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.
mark-project-as-template 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.