security_enforce · Git Steer MCP: Risk & Policy

WHAT IT DOES

What security_enforce does on Git Steer

AI agents use security_enforce 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 security_enforce needs a policy

This tool modifies repository security settings by enabling Dependabot alerts and automated security fixes. It creates or updates configuration state across repositories, which is a reversible write operation.

From the tool's definition Ensure Dependabot vulnerability alerts and automated security fixes are enabled on all managed repos

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

security_enforce Rate-limited

security_enforce 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": {
    "security_enforce": {
      "limits": [
        {
          "counter": "security_enforce_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 security_enforce

What does the security_enforce tool do? +

Ensure Dependabot vulnerability alerts and automated security fixes are enabled on all managed repos (or a specific repo). 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 security_enforce? +

Register the Git Steer MCP server in PolicyLayer and add a rule for security_enforce: 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 security_enforce? +

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

Can I rate-limit security_enforce? +

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

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

security_enforce 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.