steer_sync

Force sync state to GitHub

Server Git Steer ry-ops/git-steer
Category Write
Risk class Medium
Parameters 00 required

What steer_sync does on Git Steer

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

The tool pushes/syncs configuration and audit log state to a private GitHub repository. 'Force sync' implies writing data to GitHub (committing/pushing state), which is a Write operation. It could overwrite existing state, but 'sync' typically implies an update rather than irreversible deletion.

From the tool's definition Force sync state to GitHub

Questions about steer_sync

What does the steer_sync tool do? +

Force sync state to GitHub. 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 steer_sync? +

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

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

Can I rate-limit steer_sync? +

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

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

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.