add_mac_registration
Register a MAC address for Central NAC. mac_address e.g. 'aa:bb:cc:dd:ee:ff'.
This record as markdown: /tools/secure-ssid-centralmcp/add-mac-registration.md
What add_mac_registration does on API-Central
AI agents use add_mac_registration to create or update resources in API-Central, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.
Why add_mac_registration is rated Medium
This tool creates a new MAC address registration in the Network Access Control system. It modifies the NAC database by adding an entry, which is a write-class operation. The severity is medium because while it could be misused to register unauthorized devices on the network (affecting network access control policies), the action is reversible through deletion of the registration.
From the tool's definition 'Register a MAC address for Central NAC' - the tool creates/registers a new MAC address entry in the NAC system, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs add_mac_registration safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_mac_registration, this is the rule to start with:
add_mac_registration stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every add_mac_registration call is checked against it from then on.
Questions about add_mac_registration
Register a MAC address for Central NAC. mac_address e.g. 'aa:bb:cc:dd:ee:ff'. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the API-Central MCP server in PolicyLayer and add a rule for add_mac_registration: 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 API-Central. Nothing to install.
add_mac_registration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_mac_registration 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 add_mac_registration. 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.
add_mac_registration is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue