Critical Risk →

github_delete_repository

Delete a repository (requires admin access)

Admin/system-level operation

Part of the Github Mcp Server Sls C4d5e6f7 A8b9 4012 B345 456789012345 MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call github_delete_repository to permanently remove or destroy resources in Github Mcp Server Sls C4d5e6f7 A8b9 4012 B345 456789012345. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call github_delete_repository in a loop, permanently destroying resources in Github Mcp Server Sls C4d5e6f7 A8b9 4012 B345 456789012345. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

github-mcp-server-sls-c4d5e6f7-a8b9-4012-b345-456789012345.yaml
tools:
  github_delete_repository:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Github Mcp Server Sls C4d5e6f7 A8b9 4012 B345 456789012345 policy for all 138 tools.

Tool Name github_delete_repository
Category Destructive
Risk Level Critical

View all 138 tools →

Agents calling destructive-class tools like github_delete_repository have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

github_delete_repository is one of the critical-risk operations in Github Mcp Server Sls C4d5e6f7 A8b9 4012 B345 456789012345. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the github_delete_repository tool do? +

Delete a repository (requires admin access). It is categorised as a Destructive tool in the Github Mcp Server Sls C4d5e6f7 A8b9 4012 B345 456789012345 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on github_delete_repository? +

Add a rule in your Intercept YAML policy under the tools section for github_delete_repository. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Github Mcp Server Sls C4d5e6f7 A8b9 4012 B345 456789012345 MCP server.

What risk level is github_delete_repository? +

github_delete_repository is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit github_delete_repository? +

Yes. Add a rate_limit block to the github_delete_repository rule in your Intercept 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.

How do I block github_delete_repository completely? +

Set action: deny in the Intercept policy for github_delete_repository. 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.

What MCP server provides github_delete_repository? +

github_delete_repository is provided by the Github Mcp Server Sls C4d5e6f7 A8b9 4012 B345 456789012345 MCP server (@coretext-ai/github-mcp-server-sls-c4d5e6f7-a8b9-4012-b345-456789012345). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Github Mcp Server Sls C4d5e6f7 A8b9 4012 B345 456789012345

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.