Return the configured project roots that this MCP server may access.
AI agents call list_allowed_roots to retrieve information from Local Code 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 configuration data about allowed directory access. It performs a simple lookup/retrieval with no ability to modify, delete, or execute anything. The information returned is metadata about access permissions rather than actual file or system data, making it a low-severity read operation.
From the tool's definition Tool name 'list_allowed_roots' and description 'Return the configured project roots' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Return the configured project roots that this MCP server may access. It is categorised as a Read tool in the Local Code MCP Server, which means it retrieves data without modifying state.
Register the Local Code MCP server in PolicyLayer and add a rule for list_allowed_roots: 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 Local Code. Nothing to install.
list_allowed_roots 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 list_allowed_roots 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 list_allowed_roots. 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.
list_allowed_roots is provided by the Local Code MCP server (js190-prog/local-code-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 →