Create or update a switch port profile and scope-map it.
AI agents use create_port_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.
This tool creates or updates switch port profiles, which are reversible configuration changes to network infrastructure. It modifies data (port configurations) but does not delete, destroy, execute arbitrary code, or move money. The medium severity reflects that misconfiguration could impact network availability or security posture, but changes are generally reversible through subsequent updates or deletions.
From the tool's definition Tool name 'create_port_profile' and description 'Create or update a switch port profile and scope-map it' explicitly indicate creation and modification of network configuration data.
Attacks that exploit this kind of access
Create or update a switch port profile and scope-map it. 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 create_port_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.
create_port_profile 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 create_port_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.
Set action: deny in the PolicyLayer policy for create_port_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.
create_port_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.
create_port_profile is one line of API-Central's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →