📋 List all IndexFoundry projects. 📁 STORAGE LOCATION: All projects are stored in: {indexfoundry-install-path}/projects/ Each project has its own subdirectory with data/, src/, and frontend/. USE WHEN: You need to see what projects exist or check their stats RETURNS: Array of { project_id, name,...
AI agents call indexfoundry_project_list to retrieve information from IndexFoundry MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a retrieval operation that queries project metadata with no side effects. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because exposure only reveals project names and metadata, with minimal blast radius if misused by an agent.
From the tool's definition Tool name and description explicitly indicate listing functionality: 'List all IndexFoundry projects' returning 'Array of { project_id, name, created_at, stats? }'. No creation, modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
📋 List all IndexFoundry projects. 📁 STORAGE LOCATION: All projects are stored in: {indexfoundry-install-path}/projects/ Each project has its own subdirectory with data/, src/, and frontend/. USE WHEN: You need to see what projects exist or check their stats RETURNS: Array of { project_id, name, created_at, stats? }. It is categorised as a Read tool in the IndexFoundry MCP MCP Server, which means it retrieves data without modifying state.
Register the IndexFoundry MCP server in PolicyLayer and add a rule for indexfoundry_project_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the indexfoundry_project_list 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_list. 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_list 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 →