Create a device-side MAC-auth (MAB) profile via POST /macauth/{name}.
AI agents use create_aaa_macauth_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 a new MAC authentication profile, which is a reversible configuration change. It modifies network security settings by adding a new authentication mechanism, but the action can be undone by deleting the profile. It does not execute arbitrary code, delete data, or involve financial transactions.
From the tool's definition Tool description explicitly states 'Create a device-side MAC-auth (MAB) profile via POST /macauth/{name}'. The POST HTTP method and 'Create' action indicate data creation.
Attacks that exploit this kind of access
Create a device-side MAC-auth (MAB) profile via POST /macauth/{name}. 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_aaa_macauth_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_aaa_macauth_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_aaa_macauth_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_aaa_macauth_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_aaa_macauth_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.
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 →