Get Tx/Rx byte and packet counters for CX switch interfaces.
AI agents call get_switch_interface_counters 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 network interface statistics (transmit/receive bytes and packets) without modifying, deleting, or executing operations. It is purely observational/monitoring in nature, consistent with the 'Read' category for tools that retrieve or query data with no side effects.
From the tool's definition Tool name and description indicate it retrieves counter data ('Get Tx/Rx byte and packet counters') from switch interfaces. The verb 'Get' and the focus on retrieving existing metrics with no modification capability indicate a read-only query operation.
Attacks that exploit this kind of access
Get Tx/Rx byte and packet counters for CX switch interfaces. 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_switch_interface_counters: 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_switch_interface_counters 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_switch_interface_counters 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_switch_interface_counters. 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_switch_interface_counters 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 →