ℹ️ Get IndexFoundry server installation information. WHAT THIS RETURNS: - server_base_dir: Where IndexFoundry is installed - projects_dir: Where all projects are stored - runs_dir: Where run-based pipeline artifacts are stored USE WHEN: - You need to tell users where their projects are stored - Y...
AI agents call indexfoundry_get_server_info 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 tool is purely informational and read-only. It queries and returns configuration and directory information about the IndexFoundry installation without side effects or risk of data modification or external action execution.
From the tool's definition The tool retrieves server metadata: 'Get IndexFoundry server installation information' returning 'server_base_dir', 'projects_dir', and 'runs_dir'. No modification, deletion, or execution occurs.
Attacks that exploit this kind of access
ℹ️ Get IndexFoundry server installation information. WHAT THIS RETURNS: - server_base_dir: Where IndexFoundry is installed - projects_dir: Where all projects are stored - runs_dir: Where run-based pipeline artifacts are stored USE WHEN: - You need to tell users where their projects are stored - You need to reference absolute paths in other tools - You want to verify the IndexFoundry installation This is helpful for explaining to users that projects they create are stored within the IndexFoundry installation directory, not in their working directory. 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_get_server_info: 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_get_server_info 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_get_server_info 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_get_server_info. 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_get_server_info 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 →