sc_checkin
Check in file(s) to source control with a description.
This record as markdown: /tools/jjpxdev-unreal-mcp/sc-checkin.md
What sc_checkin does on Unreal
AI agents use sc_checkin to create or update resources in Unreal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unreal environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
paths | array | Yes | File paths to check in |
description | string | Yes | Check-in description / commit message |
Parameters from the server's own tool schema.
Why sc_checkin is rated Medium
Checking in files to source control creates new commits/versions and modifies the repository state. While reversible (prior versions remain accessible and commits can be reverted), this is a write operation that introduces changes to the tracked codebase. The severity is medium because misuse could pollute the repository history or introduce unwanted code, but commits can be reverted and are auditable.
From the tool's definition Tool name 'sc_checkin' and description 'Check in file(s) to source control with a description' indicates it modifies source control state by committing/checking in files, which is a reversible write operation to a version control system.
Attacks that exploit this kind of access
The rule that runs sc_checkin safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unreal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sc_checkin, this is the rule to start with:
sc_checkin 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 Unreal, apply this rule, and every sc_checkin call is checked against it from then on.
Questions about sc_checkin
Check in file(s) to source control with a description. It is categorised as a Write tool in the Unreal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sc_checkin accepts 2 parameters: paths, description. Required: paths, description. The full parameter table on this page comes from the server's own tool schema.
Register the Unreal MCP server in PolicyLayer and add a rule for sc_checkin: 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 Unreal. Nothing to install.
sc_checkin 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 sc_checkin 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 sc_checkin. 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.
sc_checkin is provided by the Unreal MCP server (@jjpxdev/unreal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unreal, and thousands of servers like it.
This server
Across the catalogue