github_set_secret
Create / update a repo secret for GitHub Actions.
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.
Attacks that exploit this kind of access
The rule that runs github_set_secret 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_set_secret, this is the rule to start with:
github_set_secret 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_set_secret call is checked against it from then on.
Questions about github_set_secret
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.
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.
github_set_secret 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_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.
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.
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.
This server
Across the catalogue