Sets a repository, organization, or environment GitHub Actions secret. Secret values are sent via stdin and never returned.
AI agents use secret-set to create or update resources in Make — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Make environment.
This tool creates or modifies GitHub Actions secrets, which are sensitive configuration data. While secrets are not monetary, the action is reversible (secrets can be updated or deleted), placing it in Write rather than Destructive. The severity is high because misuse could expose sensitive credentials across CI/CD pipelines, potentially compromising infrastructure, API keys, or deployment credentials.
From the tool's definition Tool description states it 'Sets a repository, organization, or environment GitHub Actions secret', indicating modification of sensitive configuration data. The mechanism of accepting secret values via stdin confirms intent to persist credentials/secrets.
Documented attack patterns abuse exactly the kind of access secret-set gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for secret-set:
{
"version": "1",
"default": "deny",
"tools": {
"secret-set": {
"limits": [
{
"counter": "secret-set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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 Make MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Make 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 Make. 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 Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.