8 tools. 4 can modify or destroy data without limits.
4 write tools that can modify data. Rate limits recommended.
Last updated:
Community server · catalogue entry verified 30/06/2026
Running more than one server? Check your whole stack →
4 of Mcp Github Pm's 8 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Github Pm, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"add_labels": {
"limits": [
{
"counter": "add_labels_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"generate_changelog": {
"limits": [
{
"counter": "generate_changelog_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
The Mcp Github Pm server has 4 write tools including add_labels, create_issue, create_milestone. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Mcp Github Pm.
8 tools across 2 categories: Read, Write. 4 are read-only. 4 can modify, create, or delete data.
Register the Mcp Github Pm MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 8 Mcp Github Pm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
8 Mcp Github Pm tools catalogued and risk-classified — across an index of 43,000+ MCP servers.