Low Risk

switch_repository

Switch to a different initialized repository.

How to control switch_repository ↓

What switch_repository does on Nuanced MCP Server

AI agents call switch_repository to retrieve information from Nuanced 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 switch_repository needs a policy

This tool changes the active repository context for analysis purposes. It does not create, modify, delete, or execute anything — it simply selects which already-initialized repository to work with. The effect is a state change in the MCP session context, analogous to a 'cd' or 'use' command. No data is written or destroyed, and no external operations are triggered.

From the tool's definition Switch to a different initialized repository

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

How to control switch_repository

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

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

switch_repository 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 Nuanced 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 switch_repository

What does the switch_repository tool do? +

Switch to a different initialized repository. It is categorised as a Read tool in the Nuanced MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on switch_repository? +

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

What risk level is switch_repository? +

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

Can I rate-limit switch_repository? +

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

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

switch_repository is provided by the Nuanced MCP Server MCP server (mattmorgis/nuanced-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nuanced MCP Server tool call.

Start from Nuanced 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.

6 Nuanced 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.