New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

transport_status

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-status.md

What transport_status does on Nogra

AI agents call transport_status 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.

Why transport_status is rated Low

The name 'transport_status' most naturally implies retrieving or checking the status of a transport/operation, which is a read-only operation. Lack of descriptive text lowers confidence but the semantic meaning of 'status' queries—querying current state without modification—points to the Read category. No evidence of side effects, destructive capability, or financial impact.

From the tool's definition Tool name 'transport_status' suggests querying status information. Description is empty, limiting direct evidence. Context indicates this is a Nogra server focused on verification and trust layers with no credentials.

Questions about transport_status

What does the transport_status tool do? +

transport_status 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_status? +

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

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

Can I rate-limit transport_status? +

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

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

transport_status 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.

More on Nogra, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nogra's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.