github_add_readme_badges
A write tool on the Github MCP server.
This record as markdown: /tools/dkeeno-github-mcp-server/github-add-readme-badges.md
What github_add_readme_badges does on Github
AI agents use github_add_readme_badges 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_add_readme_badges is rated Medium
Adding badges to a README is a reversible write operation that creates or modifies file content in a repository. While it changes repository state, it is not destructive (the original content remains recoverable via git history) and does not execute arbitrary code or delete data. The empty description lowers confidence slightly, but the action implied by the name is clearly a content modification (Write category).
From the tool's definition Tool name 'github_add_readme_badges' indicates modification of repository README file by adding badges. Server description explicitly mentions 'repository management' and the tool operates within a GitHub operations context where such actions modify…
Attacks that exploit this kind of access
The rule that runs github_add_readme_badges safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Github, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_add_readme_badges, this is the rule to start with:
github_add_readme_badges 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every github_add_readme_badges call is checked against it from then on.
Questions about github_add_readme_badges
github_add_readme_badges 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.
Register the Github MCP server in PolicyLayer and add a rule for github_add_readme_badges: 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.
github_add_readme_badges 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 github_add_readme_badges 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 github_add_readme_badges. 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.
github_add_readme_badges 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.
This server
Across the catalogue