📥 [STEP 2/5: ADD] Add data source(s) to a project. PREREQUISITES: project_create must have been run first SOURCE TYPES (use exactly one per source): - url: Single webpage (HTML content extracted) - sitemap_url: Crawl all pages in sitemap.xml - folder_path: Local folder with text/markdown/PDF fil...
AI agents use indexfoundry_project_add_source to create or update resources in IndexFoundry MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IndexFoundry MCP environment.
This tool creates or modifies project state by ingesting and registering data sources (URLs, sitemaps, folder paths, PDFs) into a vector database project. While reversible (sources can presumably be removed), it permanently alters the indexed content and project configuration.
From the tool's definition Tool description explicitly states '[STEP 2/5: ADD] Add data source(s) to a project' and lists SOURCE TYPES for ingesting content into a project. The verb 'Add' and the word 'source(s)' indicate data is being written/created into the vector database project.
Attacks that exploit this kind of access
📥 [STEP 2/5: ADD] Add data source(s) to a project. PREREQUISITES: project_create must have been run first SOURCE TYPES (use exactly one per source): - url: Single webpage (HTML content extracted) - sitemap_url: Crawl all pages in sitemap.xml - folder_path: Local folder with text/markdown/PDF files - pdf_path: Single PDF file (local path or URL) MODES: - Single: Provide one source directly in parameters - Batch: Use \. It is categorised as a Write tool in the IndexFoundry MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IndexFoundry MCP server in PolicyLayer and add a rule for indexfoundry_project_add_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 IndexFoundry MCP. Nothing to install.
indexfoundry_project_add_source 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 indexfoundry_project_add_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.
Set action: deny in the PolicyLayer policy for indexfoundry_project_add_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.
indexfoundry_project_add_source is provided by the IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.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 →