github_push_portfolio

A write tool on the Github MCP server.

SERVERGithub SOURCEdkeeno/github-mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-github-mcp-server/github-push-portfolio.md

What github_push_portfolio does on Github

AI agents use github_push_portfolio to create or update resources in Github, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Github environment.

Why github_push_portfolio is rated Medium

This tool creates new GitHub repositories from local folders. Repository creation is a Write-category action because it modifies GitHub state by adding new repositories, which can be reversed (by deleting the repo). It is not Destructive because creation is reversible. Severity is high due to the potential for creating numerous unauthorized or malicious repositories if misused by an AI agent.

From the tool's definition Tool name 'github_push_portfolio' combined with server description stating it is 'a unique portfolio push tool to create repos from local folders.' The 'push' operation and 'create repos' language indicate repository creation, which is a Write operation…

Questions about github_push_portfolio

What does the github_push_portfolio tool do? +

github_push_portfolio is a write tool on the Github MCP server. It is categorised as a Write tool in the Github MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on github_push_portfolio? +

Register the Github MCP server in PolicyLayer and add a rule for github_push_portfolio: 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. Nothing to install.

What risk level is github_push_portfolio? +

github_push_portfolio is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit github_push_portfolio? +

Yes. Add a rate_limit block to the github_push_portfolio 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.

How do I block github_push_portfolio completely? +

Set action: deny in the PolicyLayer policy for github_push_portfolio. 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_push_portfolio? +

github_push_portfolio is provided by the Github MCP server (dkeeno/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Github, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Github's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.