transport_abort

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/transport-abort.md

WHAT IT DOES

What transport_abort does on Nogra

AI agents call transport_abort 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 transport_abort is rated Low

Even though transport_abort 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 transport_abort 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 transport_abort, this is the rule to start with:

transport_abort Allowed

transport_abort 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": {
    "transport_abort": {}
  }
}

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 transport_abort call is checked against it from then on.

FAQ

Questions about transport_abort

What does the transport_abort tool do? +

transport_abort 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 transport_abort? +

Register the Nogra MCP server in PolicyLayer and add a rule for transport_abort: 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 transport_abort? +

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

Can I rate-limit transport_abort? +

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

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

transport_abort 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 →