Get LLDP neighbor table from a CX switch.
AI agents call get_lldp_neighbors 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 LLDP (Link Layer Discovery Protocol) neighbor information from a network switch. LLDP neighbor discovery is a read-only operation that provides visibility into connected network devices without modifying any configuration or state. No data is created, modified, deleted, or executed as a side effect. This is purely informational retrieval.
From the tool's definition Tool description: 'Get LLDP neighbor table from a CX switch.' The verb 'Get' and action of retrieving a neighbor table indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get LLDP neighbor table from a CX switch. 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 get_lldp_neighbors: 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.
get_lldp_neighbors 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 get_lldp_neighbors 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 get_lldp_neighbors. 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.
get_lldp_neighbors 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 →