sync_project · Synapse MCP: Risk & Policy

WHAT IT DOES

What sync_project does on Synapse

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

WHY IT NEEDS A POLICY

Why sync_project needs a policy

Syncing the graph with the filesystem state involves reading files and writing/updating the graph database to reflect current code structure. This is a Write operation (creating or modifying data reversibly in the graph), not Destructive since it's a sync operation that updates rather than irreversibly deletes.

From the tool's definition "Sync the graph with the current filesystem state"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_project Rate-limited

sync_project 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": {
    "sync_project": {
      "limits": [
        {
          "counter": "sync_project_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 Synapse, so you can run agents against it safely.

FAQ

Questions about sync_project

What does the sync_project tool do? +

Sync the graph with the current filesystem state. It is categorised as a Write tool in the Synapse MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sync_project? +

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

What risk level is sync_project? +

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

Can I rate-limit sync_project? +

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

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

sync_project is provided by the Synapse MCP server (synappscodecomprehension/synapps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.