Ingests a file into the namespace. Supports various file formats with automatic parsing.
AI agents use ingestFile to create or update resources in SourceSync Ai MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SourceSync Ai MCP Server environment.
Ingesting a file creates new content/data within the namespace. This is a reversible write operation (documents can be deleted later), not destructive. The blast radius is medium as it could introduce unwanted or malicious content into the knowledge base.
From the tool's definition Ingests a file into the namespace. Supports various file formats with automatic parsing.
Attacks that exploit this kind of access
Ingests a file into the namespace. Supports various file formats with automatic parsing. It is categorised as a Write tool in the SourceSync Ai MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SourceSync Ai MCP Server MCP server in PolicyLayer and add a rule for ingestFile: 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.
ingestFile 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 ingestFile 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 ingestFile. 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.
ingestFile 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →