Low Risk

project_get_root

Return the current PROJECT_ROOT used by tools

How to control project_get_root ↓

What project_get_root does on 8th Wall MCP Server

AI agents call project_get_root to retrieve information from 8th Wall MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why project_get_root needs a policy

This is a simple getter that returns the current project root path. It retrieves information about the tool's operating context without performing any operations, modifying data, executing code, or causing side effects. The tool has a read-only nature with minimal security impact—knowing the project root is low risk compared to tools that create, execute, or delete resources.

From the tool's definition Tool name 'project_get_root' and description 'Return the current PROJECT_ROOT used by tools' indicate a retrieval of configuration/state information with no modification or execution capability.

Documented attack patterns abuse exactly the kind of access project_get_root gives an agent:

How to control project_get_root

PolicyLayer is an MCP gateway — it sits between your AI agents and 8th Wall MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for project_get_root:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "project_get_root": {}
  }
}

project_get_root is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register 8th Wall MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about project_get_root

What does the project_get_root tool do? +

Return the current PROJECT_ROOT used by tools. It is categorised as a Read tool in the 8th Wall MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on project_get_root? +

Register the 8th Wall MCP Server MCP server in PolicyLayer and add a rule for project_get_root: 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 8th Wall MCP Server. Nothing to install.

What risk level is project_get_root? +

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

Can I rate-limit project_get_root? +

Yes. Add a rate_limit block to the project_get_root 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 project_get_root completely? +

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

project_get_root is provided by the 8th Wall MCP Server MCP server (superdwayne/8thwallmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 8th Wall MCP Server tool call.

Start from 8th Wall MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

64 8th Wall MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.