AI agents use sync_files to create or update resources in Srunx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Srunx environment.
The name 'sync_files' strongly suggests a file synchronization operation, which typically involves creating or modifying files (Write). In a SLURM/HPC context this likely transfers files to/from a remote cluster. However, sync operations can sometimes overwrite or delete files (Destructive). With no description available, confidence is low.
From the tool's definition Tool name 'sync_files' — description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access sync_files gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Srunx, and nothing reaches the server without passing your rules. This is the rule we recommend for sync_files:
{
"version": "1",
"default": "deny",
"tools": {
"sync_files": {
"limits": [
{
"counter": "sync_files_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sync_files 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.
sync_files. It is categorised as a Write tool in the Srunx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Srunx MCP server in PolicyLayer and add a rule for sync_files: 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 Srunx. Nothing to install.
sync_files 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 sync_files 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 sync_files. 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.
sync_files is provided by the Srunx MCP server (ksterx/srunx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Srunx, 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.
14 Srunx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.