PATCH a sw-port-profile to bind mac-auth / dot1x / server-group / role.
AI agents use set_port_auth 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.
This tool modifies network switch port authentication profiles (mac-auth, dot1x, server-group, role bindings), creating or updating authentication configurations. The PATCH operation is reversible—configurations can be changed back or reconfigured.
From the tool's definition PATCH a sw-port-profile to bind mac-auth / dot1x / server-group / role — the operation modifies port authentication configuration, a critical network setting, but remains reversible through subsequent PATCH operations.
Attacks that exploit this kind of access
PATCH a sw-port-profile to bind mac-auth / dot1x / server-group / role. 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 set_port_auth: 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.
set_port_auth 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 set_port_auth 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 set_port_auth. 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.
set_port_auth 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →