Low Risk

toggle_master_solo

toggle_master_solo

How to control toggle_master_solo ↓

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

Low Risk

Even though toggle_master_solo only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

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

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

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

toggle_master_solo 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 Reaper Reapy — 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 toggle_master_solo tool do? +

toggle_master_solo. It is categorised as a Read tool in the Reaper Reapy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on toggle_master_solo? +

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

What risk level is toggle_master_solo? +

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

Can I rate-limit toggle_master_solo? +

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

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

toggle_master_solo is provided by the Reaper Reapy MCP server (wegitor/reaper-reapy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Reaper Reapy tool call.

Deterministic rules across all 47 Reaper Reapy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

47 Reaper Reapy 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.