code_file_map

Recursively map the project

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/code-file-map.md

WHAT IT DOES

What code_file_map does on FeatureBoard

AI agents call code_file_map to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why code_file_map is rated Low

A recursive project mapping operation reads the file system to build a structural map. There are no side effects, deletions, or writes implied. The main risk is exposure of sensitive file paths or contents to an AI agent, but the operation itself is read-only.

From the tool's definition "Recursively map the project" — scanning/mapping files implies reading directory structure and file contents without modification

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs code_file_map safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For code_file_map, this is the rule to start with:

code_file_map Allowed

code_file_map is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "code_file_map": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every code_file_map call is checked against it from then on.

FAQ

Questions about code_file_map

What does the code_file_map tool do? +

Recursively map the project. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on code_file_map? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for code_file_map: 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 FeatureBoard. Nothing to install.

What risk level is code_file_map? +

code_file_map is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit code_file_map? +

Yes. Add a rate_limit block to the code_file_map 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.

How do I block code_file_map completely? +

Set action: deny in the PolicyLayer policy for code_file_map. 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.

What MCP server provides code_file_map? +

code_file_map is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

read_input_file on 0gzk →claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →