Define retrieval configuration: top_k, hybrid search settings, reranking, metadata filters, and scoring adjustments.
AI agents use indexfoundry_index_build_profile 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 a retrieval/index build profile (configuration settings). It defines parameters such as top_k, hybrid search settings, and scoring adjustments — a reversible write operation that configures how queries are executed. There is no indication of code execution, deletion, or financial impact. Severity is low since misconfiguration of retrieval parameters has limited blast radius.
From the tool's definition Define retrieval configuration: top_k, hybrid search settings, reranking, metadata filters, and scoring adjustments.
Attacks that exploit this kind of access
Define retrieval configuration: top_k, hybrid search settings, reranking, metadata filters, and scoring adjustments. 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_index_build_profile: 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_index_build_profile 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_index_build_profile 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_index_build_profile. 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_index_build_profile 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 →