indexfoundry_project_remove_source

🗑️ Remove source(s) from a project with cascade deletion. PREREQUISITES: project_create must have been run MODES: - Single: Provide source_id or source_uri to remove one source - Batch: Use \

Server IndexFoundry MCP mnehmos/mnehmos.index-foundry.mcp
Category Destructive
Risk class Critical
Parameters 00 required

What indexfoundry_project_remove_source does on IndexFoundry MCP

AI agents call indexfoundry_project_remove_source to permanently remove resources in IndexFoundry MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why indexfoundry_project_remove_source needs a policy

This tool irreversibly deletes data (sources and their cascading dependencies) from a vector database project. Cascade deletion means the operation cannot be selectively undone and may remove more data than explicitly targeted.

From the tool's definition Tool name contains 'remove' and description explicitly states '🗑️ Remove source(s) from a project with cascade deletion.' The 'cascade deletion' terminology indicates irreversible removal of data and potentially dependent records.

Questions about indexfoundry_project_remove_source

What does the indexfoundry_project_remove_source tool do? +

🗑️ Remove source(s) from a project with cascade deletion. PREREQUISITES: project_create must have been run MODES: - Single: Provide source_id or source_uri to remove one source - Batch: Use \. It is categorised as a Destructive tool in the IndexFoundry MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on indexfoundry_project_remove_source? +

Register the IndexFoundry MCP server in PolicyLayer and add a rule for indexfoundry_project_remove_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.

What risk level is indexfoundry_project_remove_source? +

indexfoundry_project_remove_source is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit indexfoundry_project_remove_source? +

Yes. Add a rate_limit block to the indexfoundry_project_remove_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.

How do I block indexfoundry_project_remove_source completely? +

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

What MCP server provides indexfoundry_project_remove_source? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.