dispatch_handoff

A read tool on the Nogra MCP server.

SERVERNogra SOURCE@nograai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-nograai-nogra-mcp/dispatch-handoff.md

WHAT IT DOES

What dispatch_handoff does on Nogra

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

RISK

Why dispatch_handoff is rated Low

Even though dispatch_handoff 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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dispatch_handoff safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nogra, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dispatch_handoff, this is the rule to start with:

dispatch_handoff Allowed

dispatch_handoff is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dispatch_handoff": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nogra, apply this rule, and every dispatch_handoff call is checked against it from then on.

FAQ

Questions about dispatch_handoff

What does the dispatch_handoff tool do? +

dispatch_handoff is a read tool on the Nogra MCP server. It is categorised as a Read tool in the Nogra MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dispatch_handoff? +

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

What risk level is dispatch_handoff? +

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

Can I rate-limit dispatch_handoff? +

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

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

dispatch_handoff is provided by the Nogra MCP server (@nograai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nogra, and thousands of servers like it.

This server

All 45 Nogra tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →