mac_address_format
MAC Address Formatter / Decoder — Normalize a MAC address (colon/hyphen/dot/bare) to any style, extract its OUI prefix, and decode the IEEE 802 multicast (I/G) and locally-administered (U/L) bit flags.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/mac-address-format.md
What mac_address_format does on Gateway
AI agents call mac_address_format 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 |
|---|---|---|---|
mac | string | Yes | MAC address in any common separator style |
output_format | string | — | colon | hyphen | dot | bare (default colon) |
Parameters from the server's own tool schema.
Why mac_address_format is rated Low
MAC address formatting and OUI decoding are pure data transformation and lookup operations. The tool reads input, applies formatting rules, and extracts/decodes information (I/G and U/L bits) without creating, modifying, or destroying any persistent state. This is characteristic of Read category tools. Severity is low because misuse poses minimal risk—worst case is incorrect formatting output with no system impact.
From the tool's definition Tool performs format normalization, prefix extraction, and bit flag decoding on MAC addresses — operations that only retrieve or transform data without side effects. No modifications, deletions, code execution, or financial operations are possible.
Attacks that exploit this kind of access
The rule that runs mac_address_format 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 mac_address_format, this is the rule to start with:
mac_address_format 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 mac_address_format call is checked against it from then on.
Questions about mac_address_format
MAC Address Formatter / Decoder — Normalize a MAC address (colon/hyphen/dot/bare) to any style, extract its OUI prefix, and decode the IEEE 802 multicast (I/G) and locally-administered (U/L) bit flags. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
mac_address_format accepts 2 parameters: mac, output_format. Required: mac. 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 mac_address_format: 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.
mac_address_format 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 mac_address_format 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 mac_address_format. 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.
mac_address_format 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