create_mac_auth_profile · API-Central MCP: Risk & Policy

WHAT IT DOES

What create_mac_auth_profile does on API-Central

AI agents use create_mac_auth_profile 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 create_mac_auth_profile needs a policy

This tool creates a new MAC authentication profile in HPE Aruba Central, which modifies network security configuration. While reversible (profiles can be updated or deleted), it has high severity because misconfigured MAC auth profiles could impact network access control and security posture.

From the tool's definition Tool name 'create_mac_auth_profile' indicates creation of a MAC authentication profile. Sibling tools include 'add_mac_registration' and 'add_mpsk_registration', confirming this server manages network authentication configurations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_mac_auth_profile Rate-limited

create_mac_auth_profile 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": {
    "create_mac_auth_profile": {
      "limits": [
        {
          "counter": "create_mac_auth_profile_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 create_mac_auth_profile

What does the create_mac_auth_profile tool do? +

create_mac_auth_profile. 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 create_mac_auth_profile? +

Register the API-Central MCP server in PolicyLayer and add a rule for create_mac_auth_profile: 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 create_mac_auth_profile? +

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

Can I rate-limit create_mac_auth_profile? +

Yes. Add a rate_limit block to the create_mac_auth_profile 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 create_mac_auth_profile completely? +

Set action: deny in the PolicyLayer policy for create_mac_auth_profile. 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 create_mac_auth_profile? +

create_mac_auth_profile 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.