List device-fingerprinting switch profiles (bounded by default).
AI agents call list_fingerprinting_switch_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 queries and retrieves switch profile configurations for device fingerprinting. The 'list' operation is a read-only retrieval with no side effects, no data modification, and no execution of commands. The bounded nature mentioned suggests pagination/limits on results, further confirming a safe read operation.
From the tool's definition Tool name contains 'list' and description states 'List device-fingerprinting switch profiles', indicating retrieval of existing configuration data without modification or deletion.
Attacks that exploit this kind of access
List device-fingerprinting switch 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_fingerprinting_switch_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_fingerprinting_switch_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_fingerprinting_switch_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_fingerprinting_switch_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_fingerprinting_switch_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.
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 →