number_to_ordinal
Number to English Ordinal — Format a non-negative integer with its English ordinal-indicator suffix (1 -> '1st', 11 -> '11th', 21 -> '21st').
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/number-to-ordinal.md
What number_to_ordinal does on Gateway
AI agents call number_to_ordinal to retrieve information from Gateway 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 |
|---|---|---|---|
n | number | string | Yes | Non-negative integer to format |
Parameters from the server's own tool schema.
Why number_to_ordinal is rated Low
This is a pure computational utility that transforms input data into a formatted string output without any state changes, external effects, or irreversible actions. It is purely a read/compute operation with no ability to modify, execute, or destroy data. The low severity reflects that misuse by an AI agent would only produce incorrectly formatted ordinal strings, with no meaningful blast radius.
From the tool's definition Tool description states it formats a non-negative integer with ordinal-indicator suffix (1 -> '1st', 11 -> '11th', 21 -> '21st'). No side effects, data modification, code execution, deletion, or financial operations are described or implied.
Attacks that exploit this kind of access
The rule that runs number_to_ordinal safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For number_to_ordinal, this is the rule to start with:
number_to_ordinal 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 Gateway, apply this rule, and every number_to_ordinal call is checked against it from then on.
Questions about number_to_ordinal
Number to English Ordinal — Format a non-negative integer with its English ordinal-indicator suffix (1 -> '1st', 11 -> '11th', 21 -> '21st'). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
number_to_ordinal accepts 1 parameter: n. Required: n. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for number_to_ordinal: 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 Gateway. Nothing to install.
number_to_ordinal 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 number_to_ordinal 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 number_to_ordinal. 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.
number_to_ordinal is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue