ingestConnector · SourceSync Ai MCP Server MCP

WHAT IT DOES

What ingestConnector does on SourceSync Ai MCP Server

AI agents invoke ingestConnector 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 ingestConnector needs a policy

This tool triggers an external ingestion operation that processes and imports documents from a connector into the knowledge management platform. It initiates a potentially large-scale data processing job without requiring specific document IDs, making it an Execute-category action.

From the tool's definition Ingests all documents in the connector that are in backlog or failed status... triggers external ingestion operations

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ingestConnector Rate-limited

ingestConnector 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": {
    "ingestConnector": {
      "limits": [
        {
          "counter": "ingestconnector_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 ingestConnector

What does the ingestConnector tool do? +

Ingests all documents in the connector that are in backlog or failed status. No need to provide the document ids or file ids for the ingestion. Ids are already in the backlog when picked thorough the picker. If not, the user has to go through the authorization flow again, where they will be asked to pick the documents again. 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 ingestConnector? +

Register the SourceSync Ai MCP Server MCP server in PolicyLayer and add a rule for ingestConnector: 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 ingestConnector? +

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

Can I rate-limit ingestConnector? +

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

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

ingestConnector 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.