actions_secrets · Git Steer MCP: Risk & Policy

WHAT IT DOES

What actions_secrets does on Git Steer

AI agents use actions_secrets to create or update resources in Git Steer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git Steer environment.

WHY IT NEEDS A POLICY

Why actions_secrets needs a policy

This tool modifies secrets used in GitHub Actions workflows. Secrets are credentials that control access to external services, cloud platforms, and deployment targets. While not irreversible (secrets can be rotated), misuse by an AI agent could inject malicious secrets into CI/CD pipelines, leading to credential theft, unauthorized deployments, or lateral movement.

From the tool's definition Tool name 'actions_secrets' with description 'Manage Actions secrets' indicates create/modify operations on GitHub Actions secrets, which are sensitive credentials used to authenticate and authorize CI/CD workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

actions_secrets Rate-limited

actions_secrets 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": {
    "actions_secrets": {
      "limits": [
        {
          "counter": "actions_secrets_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Git Steer, so you can run agents against it safely.

FAQ

Questions about actions_secrets

What does the actions_secrets tool do? +

Manage Actions secrets. It is categorised as a Write tool in the Git Steer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on actions_secrets? +

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

What risk level is actions_secrets? +

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

Can I rate-limit actions_secrets? +

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

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

actions_secrets is provided by the Git Steer MCP server (ry-ops/git-steer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.