synchronize_source · CustomGPT MCP Server MCP: Risk & Policy

WHAT IT DOES

What synchronize_source does on CustomGPT MCP Server

AI agents invoke synchronize_source to trigger actions in CustomGPT MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why synchronize_source needs a policy

Synchronizing or refreshing a source triggers an external operation that re-fetches or re-indexes data from the source. This is not a simple read (it causes side effects) nor a pure write (it doesn't create new data), but rather executes a process/operation against an external resource.

From the tool's definition Synchronize/refresh a source

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

synchronize_source Rate-limited

synchronize_source stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "synchronize_source": {
      "limits": [
        {
          "counter": "synchronize_source_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CustomGPT MCP Server, so you can run agents against it safely.

FAQ

Questions about synchronize_source

What does the synchronize_source tool do? +

Synchronize/refresh a source. It is categorised as a Execute tool in the CustomGPT MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on synchronize_source? +

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

What risk level is synchronize_source? +

synchronize_source is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit synchronize_source? +

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

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

synchronize_source is provided by the CustomGPT MCP Server MCP server (poll-the-people/customgpt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.