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.
Attacks that exploit this kind of access
The rule that runs transport_status 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_status, this is the rule to start with:
transport_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nogra, apply this rule, and every transport_status call is checked against it from then on.
Questions about transport_status
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.
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.
transport_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
This server
Across the catalogue