add_mac_registration · API-Central MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why add_mac_registration needs a policy

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

Recommended rule Ready

Verdict

add_mac_registration Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_mac_registration": {
      "limits": [
        {
          "counter": "add_mac_registration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches API-Central, so you can run agents against it safely.

FAQ

Questions about add_mac_registration

What does the add_mac_registration tool do? +

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.

How do I enforce a policy on add_mac_registration? +

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.

What risk level is add_mac_registration? +

add_mac_registration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_mac_registration? +

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.

How do I block add_mac_registration completely? +

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.

What MCP server provides add_mac_registration? +

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.