Low Risk

get_current_root

Get the current project root configuration.

How to control get_current_root ↓

AI agents call get_current_root to retrieve information from Scopecraft Command without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns the current project root configuration without modifying, executing, or deleting any data. It is a read-only operation that retrieves existing configuration state.

From the tool's definition Tool name 'get_current_root' and description 'Get the current project root configuration' indicate a retrieval operation with no side effects.

Risk signalsAdmin/system-level operation

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Scopecraft Command, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_root:

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

get_current_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 Scopecraft Command — 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.

Go deeper

What does the get_current_root tool do? +

Get the current project root configuration. It is categorised as a Read tool in the Scopecraft Command MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_current_root? +

Register the Scopecraft Command MCP server in PolicyLayer and add a rule for get_current_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 Scopecraft Command. Nothing to install.

What risk level is get_current_root? +

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

Can I rate-limit get_current_root? +

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

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

get_current_root is provided by the Scopecraft Command MCP server (scopecraft/command). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Scopecraft Command tool call.

Deterministic rules across all 18 Scopecraft Command tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 Scopecraft Command tools catalogued and risk-classified — across an index of 42,500+ 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.