secret-set

Sets a repository, organization, or environment GitHub Actions secret. Secret values are sent via stdin and never returned.

SERVERBuild SOURCEDave-London/Pare

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/io-github-dave-london-build/secret-set.md

WHAT IT DOES

What secret-set does on Build

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

RISK

Why secret-set is rated Medium

The tool modifies GitHub Actions secrets, which are stored credentials. While this is destructive in intent (secrets should not be arbitrarily overwritten without careful review), the technical operation itself is reversible—a secret can be updated or deleted separately.

From the tool's definition Tool description: "Sets a repository, organization, or environment GitHub Actions secret." This is a write operation that creates or modifies secrets.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs secret-set safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For secret-set, this is the rule to start with:

secret-set Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "secret-set": {
      "limits": [
        {
          "counter": "secret-set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every secret-set call is checked against it from then on.

FAQ

Questions about secret-set

What does the secret-set tool do? +

Sets a repository, organization, or environment GitHub Actions secret. Secret values are sent via stdin and never returned. It is categorised as a Write tool in the Build MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on secret-set? +

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

What risk level is secret-set? +

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

Can I rate-limit secret-set? +

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

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

secret-set is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →