slaac_address
IPv6 address a host builds for itself from a /64 prefix and a MAC (SLAAC, RFC 4862). The interface id is the modified EUI-64. The prefix must be exactly 64 bits and the low 64 bits of the prefix must be zero. Also returns the link-local address and the solicited-node multicast address. Text is RF...
This record as markdown: /tools/com-it-scorptech-x402/slaac-address.md
What slaac_address does on ScorpTech x402 API
AI agents call slaac_address to retrieve information from ScorpTech x402 API 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 | |
prefix | string | Yes |
Parameters from the server's own tool schema.
Why slaac_address is rated Low
Even though slaac_address only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs slaac_address safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For slaac_address, this is the rule to start with:
slaac_address 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 ScorpTech x402 API, apply this rule, and every slaac_address call is checked against it from then on.
Questions about slaac_address
IPv6 address a host builds for itself from a /64 prefix and a MAC (SLAAC, RFC 4862). The interface id is the modified EUI-64. The prefix must be exactly 64 bits and the low 64 bits of the prefix must be zero. Also returns the link-local address and the solicited-node multicast address. Text is RFC 5952. No zone index and no IPv4 tail. Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/slaac-address. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
slaac_address accepts 2 parameters: mac, prefix. Required: mac, prefix. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for slaac_address: 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 ScorpTech x402 API. Nothing to install.
slaac_address 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 slaac_address 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 slaac_address. 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.
slaac_address is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue