Ingests raw text content into the namespace. Supports optional metadata and chunk configuration.
AI agents use ingestText 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.
This tool creates new content in the knowledge base by ingesting raw text. It is a write operation (adding/creating data) with no indication of deletion or irreversible destruction. Misuse could lead to polluting the knowledge base with unwanted content, giving it a medium severity.
From the tool's definition Ingests raw text content into the namespace. Supports optional metadata and chunk configuration.
Attacks that exploit this kind of access
Ingests raw text content into the namespace. Supports optional metadata and chunk configuration. 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 ingestText: 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.
ingestText 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 ingestText 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 ingestText. 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.
ingestText is provided by the SourceSync Ai MCP Server MCP server (sitegpt/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 →