Comprehensively scans a project directory to extract and structure code from specified file types. Generates a detailed overview of the project
AI agents call get_full_code_context to retrieve information from RAPID MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and structures existing code information from a project directory without modifying, executing, or deleting any data. It is purely informational and read-only in nature, consistent with the Read category.
From the tool's definition Tool performs 'scans' and 'extracts' code information to 'generate a detailed overview' with no mutation, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
Comprehensively scans a project directory to extract and structure code from specified file types. Generates a detailed overview of the project. It is categorised as a Read tool in the RAPID MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RAPID MCP Server MCP server in PolicyLayer and add a rule for get_full_code_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 RAPID MCP Server. Nothing to install.
get_full_code_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 get_full_code_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 get_full_code_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.
get_full_code_context is provided by the RAPID MCP Server MCP server (otdavies/rapid). 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 →