github_set_secret

Create / update a repo secret for GitHub Actions.

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-set-secret.md

What github_set_secret does on Github

AI agents use github_set_secret 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_set_secret is rated Medium

This tool performs reversible write operations (create/update) on repository secrets. While secrets are sensitive and could be misused by an AI agent to inject malicious values that affect CI/CD pipelines, the operation itself is not destructive (secrets can be updated/removed) and does not directly move money or execute arbitrary code.

From the tool's definition Tool description states 'Create / update a repo secret for GitHub Actions' - this creates or modifies secrets used in GitHub Actions workflows, which are credentials or sensitive values stored at repository level.

Questions about github_set_secret

What does the github_set_secret tool do? +

Create / update a repo secret for GitHub Actions. 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_set_secret? +

Register the Github MCP server in PolicyLayer and add a rule for github_set_secret: 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_set_secret? +

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

Can I rate-limit github_set_secret? +

Yes. Add a rate_limit block to the github_set_secret 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_set_secret completely? +

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

github_set_secret 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.

// 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.