List Central NAC authentication profiles (bounded by default).
AI agents call list_auth_profiles to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing NAC authentication profile configurations without creating, modifying, deleting, or executing any operations. It is a pure read operation with no side effects, fitting the Read category. Severity is low because listing authentication profiles provides information about security posture but does not directly enable unauthorized access or changes without additional tools.
From the tool's definition Tool name 'list_auth_profiles' and description 'List Central NAC authentication profiles' indicate a query/retrieval operation with no modification or execution capability. The phrase 'bounded by default' suggests appropriate access controls.
Attacks that exploit this kind of access
List Central NAC authentication profiles (bounded by default). It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for list_auth_profiles: 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.
list_auth_profiles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_auth_profiles 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 list_auth_profiles. 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.
list_auth_profiles 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.
list_auth_profiles 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 →