carry_order_check

No account needed. The status of a Get carried today order by its reference.

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/carry-order-check.md

WHAT IT DOES

What carry_order_check does on Rokha

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

Parameter	Type	Required	Description
`reference`	string	Yes

Parameters from the server's own tool schema.

RISK

Why carry_order_check is rated Low

Retrieves order status without modification, side effects, or financial transactions.

From the tool's definition status of a Get carried today order by its reference

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs carry_order_check safely

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

carry_order_check Allowed

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

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

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

FAQ

Questions about carry_order_check

What does the carry_order_check tool do? +

No account needed. The status of a Get carried today order by its reference. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

What parameters does carry_order_check accept? +

carry_order_check accepts 1 parameter: reference. Required: reference. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on carry_order_check? +

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

What risk level is carry_order_check? +

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

Can I rate-limit carry_order_check? +

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

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

carry_order_check is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

The MCP Attack Database →

Guides

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