Complete index JSON trimmed to fit a specified token budget.
AI agents call get_full_index to retrieve information from Rails Insight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns index data about a Rails codebase. It performs no mutations, does not execute code, and does not delete or move data. The token budget parameter is a read-side optimization. Given the context of a codebase indexer and sibling tools that similarly retrieve information (get_overview, get_model, get_routes, etc.), this is a safe Read operation with minimal blast radius if misused.
From the tool's definition get_full_index retrieves a 'Complete index JSON' with a token budget constraint; the verb 'get' and the retrieval-only nature indicate data querying with no modification or execution.
Attacks that exploit this kind of access
Complete index JSON trimmed to fit a specified token budget. It is categorised as a Read tool in the Rails Insight MCP Server, which means it retrieves data without modifying state.
Register the Rails Insight MCP server in PolicyLayer and add a rule for get_full_index: 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 Rails Insight. Nothing to install.
get_full_index 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 get_full_index 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 get_full_index. 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.
get_full_index is provided by the Rails Insight MCP server (@reinteractive/rails-insight). 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 →