ads_order_check
Re-checks the chain for order #id and returns it — active means it is live in the agent's memory now. Requires Authorization: Bearer <JWT>.
This record as markdown: /tools/ai-rokha-rokha/ads-order-check.md
What ads_order_check does on Rokha
AI agents call ads_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 |
|---|---|---|---|
id | integer | Yes |
Parameters from the server's own tool schema.
Why ads_order_check is rated Low
Tool retrieves order status from a registry without modifying or executing external operations.
From the tool's definition Re-checks the chain for order #id and returns it
Attacks that exploit this kind of access
The rule that runs ads_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 ads_order_check, this is the rule to start with:
ads_order_check 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 Rokha, apply this rule, and every ads_order_check call is checked against it from then on.
Questions about ads_order_check
Re-checks the chain for order #id and returns it — active means it is live in the agent's memory now. Requires Authorization: Bearer <JWT>. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
ads_order_check accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for ads_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.
ads_order_check 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 ads_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.
Set action: deny in the PolicyLayer policy for ads_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.
ads_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.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue