Scan the codebase and assemble the most relevant file chunks based on a query.
AI agents call india_mcp_assemble_context to retrieve information from Neuroverse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries codebase data to return relevant file chunks in response to a query. It performs no writes, deletions, code execution, or side effects beyond information retrieval. The 'assemble' operation is aggregation of read data, not transformation or modification of the underlying codebase. This is a straightforward Read category tool with low severity.
From the tool's definition Tool description states 'Scan the codebase and assemble the most relevant file chunks based on a query' — core actions are scanning and retrieving (reading) file content with no modification or deletion.
Attacks that exploit this kind of access
Scan the codebase and assemble the most relevant file chunks based on a query. It is categorised as a Read tool in the Neuroverse MCP Server, which means it retrieves data without modifying state.
Register the Neuroverse MCP server in PolicyLayer and add a rule for india_mcp_assemble_context: 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 Neuroverse. Nothing to install.
india_mcp_assemble_context 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 india_mcp_assemble_context 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 india_mcp_assemble_context. 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.
india_mcp_assemble_context is provided by the Neuroverse MCP server (joshua400/neuroverse). 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 →