secret-set
Sets a repository, organization, or environment GitHub Actions secret. Secret values are sent via stdin and never returned.
This record as markdown: /tools/io-github-dave-london-npm/secret-set.md
What secret-set does on Npm
AI agents use secret-set to create or update resources in Npm, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Npm environment.
Why secret-set is rated Medium
This tool creates or modifies secrets in GitHub, which is a reversible write operation (secrets can be updated or deleted later). It is not Destructive because secret updates are not irreversible. However, it carries high severity because misconfigured secrets could expose credentials, compromise CI/CD pipelines, or grant unintended access to protected repositories.
From the tool's definition 'Sets a repository, organization, or environment GitHub Actions secret' - creates and modifies secrets in GitHub infrastructure; 'Secret values are sent via stdin and never returned' - confirms write operation that persists authentication/credential data
Attacks that exploit this kind of access
The rule that runs secret-set safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Npm, 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 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 Npm, apply this rule, and every secret-set call is checked against it from then on.
Questions about secret-set
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 Npm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Npm 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 Npm. Nothing to install.
secret-set 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 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.
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.
secret-set is provided by the Npm MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Npm, and thousands of servers like it.
This server
Across the catalogue