resyncDocuments · SourceSync Ai MCP Server MCP

WHAT IT DOES

What resyncDocuments does on SourceSync Ai MCP Server

AI agents invoke resyncDocuments to trigger actions in SourceSync Ai 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 resyncDocuments needs a policy

'Reprocesses' indicates re-running a processing/ingestion pipeline on existing documents. This is an execution of an operation (triggering external processing) rather than a simple read or write. It can affect potentially many documents matching filter criteria (blast radius is medium), but it doesn't irreversibly delete data, making Execute the most appropriate category.

From the tool's definition Reprocesses documents that match the specified filter criteria. Useful for updating after schema changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resyncDocuments Rate-limited

resyncDocuments 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": {
    "resyncDocuments": {
      "limits": [
        {
          "counter": "resyncdocuments_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 SourceSync Ai MCP Server, so you can run agents against it safely.

FAQ

Questions about resyncDocuments

What does the resyncDocuments tool do? +

Reprocesses documents that match the specified filter criteria. Useful for updating after schema changes. It is categorised as a Execute tool in the SourceSync Ai 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 resyncDocuments? +

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

What risk level is resyncDocuments? +

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

Can I rate-limit resyncDocuments? +

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

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

resyncDocuments is provided by the SourceSync Ai MCP Server MCP server (scmdr/sourcesyncai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

resyncDocuments is one line of SourceSync Ai MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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