Low Risk

send_get_routing_diagram

Get full project routing diagram (sends, receives, outputs).

How to control send_get_routing_diagram ↓

What send_get_routing_diagram does on ReaperMCP

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

Low Risk

Why send_get_routing_diagram needs a policy

The tool retrieves and displays routing information from the REAPER project. It is a read-only query with no side effects, simply returning a diagram of the current signal routing configuration.

From the tool's definition Get full project routing diagram (sends, receives, outputs)

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

How to control send_get_routing_diagram

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

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

send_get_routing_diagram 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 ReaperMCP — 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 send_get_routing_diagram

What does the send_get_routing_diagram tool do? +

Get full project routing diagram (sends, receives, outputs). It is categorised as a Read tool in the ReaperMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on send_get_routing_diagram? +

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

What risk level is send_get_routing_diagram? +

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

Can I rate-limit send_get_routing_diagram? +

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

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

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

Enforce policy on every ReaperMCP tool call.

Start from ReaperMCP, 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.

138 ReaperMCP 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.